Sounds good. Does it need to be a different TestRunner, or could it just enhance the existing?
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? Cheers Dan [1] http://kentbeck.github.com/junit/javadoc/latest/org/junit/rules/MethodRule.html On 8 December 2011 13:45, Kevin Meyer - KMZ <[email protected]> wrote: > > By the way, I wrote another TestCase runner based on the > IsisTestRunner that allows you to override the default in-memory or > No-op Persistor, Authenticator and Authorizer by specifying > alternatives via annotations > (@Persistor(newPersistenceMechanismInstaller.class)) etc. > > I wanted to run tests but against my own implementations of the above > / live database, etc. > > I'll check it in later once I'm finished with my current deploy. > > I'll put it in the same package as the current IsisTestRunner. > > Regards, > Kevin > >
