Notify jUnit of test system exceptions #716
… formatter) are added
I was wondering about that myself. In my real-world environment I had a test that caused Slim to be aborted. But I don't think I can introduce that in the unit-test set of FitNesse, without breaking its unit test suite.
Maybe we can use an in-memory wiki-page, combined with a mock notifier. But I saw no way to easily wire that up, not in any way that was proportional in complexity to the change itself. Do you see a way to do that?
I did not think just calling the method directly (i.e. NOT in context of a run by MultipleTestsRunner) and seeing that the notifier was called (i.e. a true unit-test) was a test that added much value. That could easily be done, of course.