I figured the dev list is the most appropriate place for this question since it has to do with how Tapestry is distributed.
Currently, in both Equinox and AppFuse, I have a tapestry-mock.jar that I created from the Tapestry 3.0's CVS - specifically org.apache.tapestry.junit, as well as org.apache.tapestry.junit.mock and org.apache.tapestry.junit.engine. In addition, I have an AbstractInstantiator.java (from Tapestry Test Assist) and a MockRequestCycle.java that I can add request parameters and such to. I'd rather not maintain my own mechanism for testing Tapestry pages out-of-container. 1. Will Tapestry 4.0 be providing a mechanism (and documentation) to test page classes? 2. If not, is it possible to add something to simplify testing for users? I'd be happy to contribute what I use - but I suspect the Tapestry developers can do a much better job than I have. Thanks, Matt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
