For unit testing, you don't ... you just let the parameters act like normal fields.
For integration testing ... you let Tapestry set up the infrastructure, whether as part of PageTester or when testing using Selenium or a similar tool. The only thing I tend to mock is ComponentResources.isBound(). On Dec 1, 2007 2:12 PM, Kevin Menard <[EMAIL PROTECTED]> wrote: > Hi all, > > I've been trying to figure out how to test components all afternoon. In the > process I've learned quite a bit, but I've yet to figure out how to mock the > binding of parameters to values. Any pointers would be much appreciated. > > Thanks, > Kevin > > -- > Kevin Menard > Servprise International, Inc. > Remote reboot & power control for network equipment > www.servprise.com +1 508.892.3823 x308 > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship TWD Consulting, Inc. Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
