I took a look at the code, ironically the TestBase which I'm using and
has all the methods public is the one depending on @AfterMethod
invocation. Of course I can just call cleanUpControlSource() in my
tearDown() method in junit and achieve the same thing. Sure I can do
what Patrick said and copy
Why not just copy to code and do whatever conversion you need to do...
probably simplest in the long run ??
All you'd need to do is expose have some method I can call
before/after, and I could do it manually. I'm using TestBase right now
because it exposes public methods (at least for the vital
newInstance() support). In the end JUnit and TestNG don't differ that
much. All the differences really boil do
Yes for reasons like this . :)
I would be ok with supporting junit (somehow) but don't know how the
EasyMock parts are supposed to get handled there as the top level base class
(which isn't BaseComponentTestCase) relies on @BeforeMethod / @AfterMethod
annotations to do before/after cleanup calls.
Without getting into a testng vs junit debate, I find the
BaseComponentTestCase class in tapestry-test very useful. However, in
the project I am working on we are using junit. It would be great if
this class could be used as a helper class without needing to extend
it, yet all the useful methods a
