Hi Fed, The only explanation I have is that there is some leftover of a previous cactus framework jar on the server side. Indeed, the line numbers do not match the Cactus 1.5dev version which supports this feature...
I have also included a pure junit TestCase as part of the Cactus test and it works fine both for Gump and for my local runs. Can you confirm? Thanks -Vincent PS: I think we need some built-in version checker which checks that both client and server are compatible. That's a nice use case for an Aspect! > -----Original Message----- > From: Fred Loney [mailto: [EMAIL PROTECTED] > Sent: 27 February 2003 18:21 > To: Cactus Dev List > Subject: RE: Cactus/Ant vs. JUnitEE > > I tried the 1.5dev ServletTestSuite solution without success. Running an > ant junit task on the TestCase described in this thread yields the > result: > > testXXX(org.apache.cactus.ServletTestCase)junit.framework.AssertionFaile > dError: Method [testXXX()] does not exist for class > [org.apache.cactus.ServletTestCase]. > at > org.apache.cactus.AbstractTestCase.runServerTest(AbstractTestCase.java:3 > 22) > at > org.apache.cactus.AbstractTestCase.runBareServerTest(AbstractTestCase.ja > va:235) > at > org.apache.cactus.server.AbstractWebTestCaller.doTest(AbstractWebTestCal > ler.java:149) > ... > > The cactus client transmits the ServletTestCase wrapper class name in > the web request rather than the wrapped TestCase class name. > > Do I need to configure cactus differently to enable use of > ServletTestCase? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
