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.
Either way I could certainly make a lot of the base methods static on some other class so that you can do static imports of them - they will just have to methods not relying on mock objects or state of any kind. (of which there are few) On 5/25/07, Daniel Tabuenca <[EMAIL PROTECTED]> wrote:
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 are listed as protected so I can't do that. Can anyone offer me suggestions on how I could use the functionality in BaseComponentTestCase without having to extend that classs? Is there a compelling reason why those methods aren't just made public? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
