run_all_test_files event

[joonty]

A potential implementation for #50.

A flag is passed from the driver to the engine to identify whether a
series of test files were queued as a result of the user triggering a
run of all the test files.

To accomplish this, I added a flag to Engine#run_test_files that states whether it was triggered by the run_all_test_files event. This flag is passed in Driver#run_all_test_files.

It feels somewhat awkward and highly specific, but I can't think of any other way of being able to trigger this event, as the running of test files is abstracted in the Driver class (which makes perfect sense).

So, it's a working solution, but one that you may or may not think could be improved upon.

[sunaku]

@joonty did you get a chance to try commit 8ca66ca in the "echo" branch? I would prefer a generic solution like that.

[joonty]

Hmm. I think I misunderstood something you said in #50:

Yes, I tried echoing but since there are so many components running in parallel, there was a multiplicative effect: 1 message caused N echo responses.

I took that to mean that you got it working, but weren't happy with it because of the event overload. I therefore went ahead and specifically implemented these events.

No problem - if you don't want to take this approach then it's fine to throw these PRs away, I'm not precious about them :)

But what's the next step in your mind?

[sunaku]

Yes, that concern about multiplying messages was about a my first shot at
implementing the echo feature.

The "echo" branch now contains a better implementation which does not
suffer from the multiplying problem.

[joonty]

Ok, I'll close these PRs in that case. Thanks