Whats the situation with abstract classes?
For the class AbstractFoo, Jumble will look for a test named DummyFooTest. This is done because there could be an actual abstract test class named AbstractFooTest. The recommended Jumble conventions are to put some unit tests for the AbstractFoo methods into the abstract AbstractFooTest class, then inherit that class into the unit tests for each subclass of AbstractFoo (say FooA and FooB). This means that JUnit will test the AbstractFoo methods for each subclass of AbstractFoo. However, the methods in AbstractFoo will not be mutated when Jumble analyses the subclasses of AbstractFoo, because it is a design principle of Jumble to analyse each class just once. So we create a DummyFooTest class that inherits AbstractFooTest, provides a “dummy” implementation of any missing methods, and concentrates on testing the methods of AbstractFoo.
