Incorrect exit code for test runner on CI, possible regression

[conzett]

This might be a regression as I see this had been addressed previously with #33 it looks like this is happening again though (no wonder all my builds were passing!) Travis logs from a recent build:

// snip
22:28:39 - ERROR - 77 specs, 4 failures
22:28:39 - INFO - Done.
22:28:39 - INFO - Guard::Jasmine stops server.
Done. Build script exited with: 0

Currently using master branch of guard-jasmine rather than a specific gem version.

[netzpirat]

Thanks for reporting. I'll have a look at it tomorrow or over the weekend. I anyway want to reflect the coverage status in the CI exit status.

[netzpirat]

The exit status works fine, but the Travis CI configuration examples in the README was wrong. We cannot use after_script for running the Jasmine specs, since that exit code has no influence on the build status. The sultion is simple, just use && to combine the two spec scripts.

[conzett]

Good call, thanks so much for your help and work on this project.