Failed test causes remainder of tests to not run

[mikestew]

Steps to repro:

1. Run bwoken with multiple .js test files. One of those test files must fail.
   Observed:
   When the failing test runs, the test run stops and the remainder of tests are not run.

When running multiple tests, if one test fails the test run stops. In practical terms, that means if one component turns buggy, tests for non-buggy components will never run (and we'll never know for sure that they're non-buggy).

It could be argued that it is preferred that as many tests are run as possible. One failing test should not stop the run. Log the failure and move on.

Perhaps it's just a difference in philosophy between me and the bwoken authors. For now I've modified script.rb so that the run method does not raise if a test fails.

[listrophy]

Regarding your last paragraph, I would tend to agree: this isn't a bug in my eyes, but a feature request. This could get added later as a command-line flag, but I'm fairly certain it won't be the default behavior.

I'd be happy to accept a PR for this if someone writes it. Otherwise, it won't be at the top of my priority list.