Hi Dan, > Sounds good. > Does it need to be a different TestRunner, or could it just enhance the > existing?
If the existing IsisTestRunner were refactored to provide override-able methods for returning the required resources, then it could be re-used. Didn't occur to me to do that. But since my new implementation is basically a copy of the IsisTestRunner with annotation support, both versions are not required (functionally, mine falls back to the same behaviour as the current one, if no annotations are detected). i.e. my new implementation will *replace* the current one. > Also, while we're on the subject, JUnit 4.7 introduced the MethodRule API > [1], which is probably the better way of doing this sort of thing. If you > raise a ticket to add in TestRunner, perhaps you could add another one too > which is to port to using this API? Will do. > > [1] > http://kentbeck.github.com/junit/javadoc/latest/org/junit/rules/MethodRule.html
