Test don't actually assert failure/success status

[ChuckJonas]

I haven't actually tested with this travis, but I'm doing pretty much the same thing with bitbucket pipelines and my tests don't actually assert a failure on the build status.

I'm thinking the best way to do this would probably be to output the results as JSON and then use a CI tool or a node script to check if there were any failures.

Not sure how it works in Travis, but in Pipelines if there is a build failure, it stops execution of the script so would want to delete the scratch org before asserting on the status of the tests.