I think that the grinder httpunit and other functional testing approaches are subtly different. We use the grinder, although I haven't, but my recollection is that it is more for load testing, rather than coverage. We use selenium (it has been custom modified) for coverage. It was difficult at first because it was not realised that mainly the only way to touch each componenet on the page was by introducing xpath, this in turn has meant examining each page using firefox's dom inspector, OK once you get into the swing of it. There are seperate issues here about unique ids for componants or lack of, entailing use of xpath. Interestingly, junit often has to behave a bit like a functional testing client using Tapestry. Here is an example:- Developing a component modification that entails the use of thread local means that the unit test must closely mirror anticipated use by the web client. Specifically new server objects should be created to be consumed in each test bank, or possibly a new unit test for this purpose. But we have other cases where using the Creator class would be very useful. I haven't done this and would like to learn more as this would be a window into the application that might make code modifications and extensions easier. Adam
On 9/9/05, Konstantin Ignatyev <[EMAIL PROTECTED]> wrote: > > The Grinder works perfectly for all kinds of web > sites, it is not limited to Tapestry. > > Examples are here: > http://kgionline.com/presentations/wa/readme/tests/technology.html > > Please ignore rest of the materials because they are > not finalized and have many broken links and errors. > > --- Henri Dupre <[EMAIL PROTECTED]> wrote: > > > On 9/9/05, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > > I haven't used grinder, but I have used httpunit > > and found it incredibly > > > painful to get working properly in junit...I'm > > using testng now but have > > > since ditched all of that code in favor of > > tapestrys built-in "Creator" > > > class. > > > > Could you elaborate on this? Is that for Tapestry > > 4?? > > Could you post one of your component testing > > example?? I'd really like > > to do that! > > > > Henri. > > > > > --------------------------------------------------------------------- > > 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] > >
