When I write unit tests for pages and components, I'm trying to test what little logic is there, basically: does the component reads its own fields (properties and parameters) and pass the right values to its injected services? Any logic much more complex than that gets shifted to the services layer, where its more obvious how to do good tests.
Of course, with Selenium (or tool du jour) you should be integration testing, to ensure that you and Tapestry agree on what data is available and when ... and to catch things like template typos and the like. On Dec 2, 2007 6:26 AM, Kevin Menard <[EMAIL PROTECTED]> wrote: > Fair enough. I didn't know if that would be considered too invasive. It > certainly would save a lot of time. > > > On 12/1/07 11:10 PM, in article > [EMAIL PROTECTED], "Howard Lewis > Ship" <[EMAIL PROTECTED]> wrote: > > > Well, you can read the field after the component logic sets it. I > > often add package-private getters and setters to facilitate testing. > > > > On Dec 1, 2007 2:34 PM, Kevin Menard <[EMAIL PROTECTED]> wrote: > > -- > > 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]
