I have now filed a JIRA issue (https://issues.apache.org/jira/browse/TAP5-643) - it seems that PageTester is using the application module defined in web.xml which is causing issues for me because of some dispatchers which will not work without external servers or the real request/response (inc. cookies) stuff.
We use PageTester to unit test the rendering of pages & components - trying to be dependent on as little else as possible. Please vote if this is affecting you too. > -----Original Message----- > From: Blower, Andy [mailto:andy.blo...@proquest.co.uk] > Sent: 03 April 2009 10:36 > To: 'Tapestry users' > Subject: RE: T5.1.0.2 problem with TestableRequestImpl > > Thanks Massimo, I'll probably file a Jira issue about this then. Weird > thing is I don't think all my tests that use PageTester are failing. I > need to investigate it, but so far I've spent a week (@50%) on moving > from 5.1.18 to 5.1.0.2 and I still don't have things working quite > right so I don't know how much time I'll be able to dedicate to this. > > > -----Original Message----- > > From: Massimo Lusetti [mailto:mluse...@gmail.com] > > Sent: 03 April 2009 10:27 > > To: Tapestry users > > Subject: Re: T5.1.0.2 problem with TestableRequestImpl > > > > On Tue, Mar 31, 2009 at 3:28 PM, Blower, Andy > > <andy.blo...@proquest.co.uk> wrote: > > > > > I'm in the process of migrating from T5.0.18 to T5.1 and I'm using > > the T5.1.0.2 release currently being voted on. I've fixed all the > > compilation errors and disabled enough of our custom stuff to get > pages > > rendering, although most of our javascript seems to be broken (I'll > be > > looking into this issue next), but I have a lot of unit tests > failing. > > Basically all of the tests using org.apache.tapestry5.test.PageTester > > to do a test render are failing with the stacktrace appended to the > > bottom of this email. This appears to be caused by the new method > > that's been added to the Request interface but not implemented in > > TestableRequestImpl. (well technically it is, but all it does is > throw > > a RuntimeException) > > > > > > So, has anyone else encountered this issue? Why aren't any of the > > Tapestry tests affected? What's the best way to fix this? > > > > I too encountered this problem but i neglected to write about it > cause > > i was already migrating to using Selenium based tests but i should > > have. > > > > If anyone would look there are example in the chenillekit-access > > module which should fire the problem. > > > > -- > > Massimo > > http://meridio.blogspot.com > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > > For additional commands, e-mail: users-h...@tapestry.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
