What about reimplementing it as a Junit rule? There are often other lifecycle bits that I want to incorporate in a unit test and having it implemented as an abstract class seems to make this difficult.
On Nov 22, 2011 5:54 PM, "Les Hazlewood" <[email protected]> wrote: While I agree that it is easy to copy-n-paste, I do believe it is easier and more convenient to just depend on a test jar, subclass the test class and be on your way writing tests. Given the two options, my vote is to create a separate 'test' module that people can depend on if they want. People can depend on it if they like, but they can just ignore it if they'd rather copy-n-paste. My .02, Les On Tue, Nov 22, 2011 at 11:45 PM, Allan Ditzel <[email protected]> wrote: > The main value woul...
