Hi, How are you folks testing your Tapestry applications? In particular I am interested in ways that allow testing complex page interactions work as they should - which is to say: 1) they don't generate excpeption pages 2) the correct page flow is observed (eg. on page A when I click next I should get page B) 3) the correct results are displayed along the way
Really, 1 & 2 are the key problems I'm hoping to nail. I am not yet sure if this needs to be performed from a client environment (ie. sending/analysing HTTP requests), or if it can somehow be tested on the server (eg. Cactus perhaps). Needless to say this testing needs to be automatable. Any suggestions/do's/don'ts would be greatly appreciated... TIA, Richard ------------------------------------------------------- This sf.net email is sponsored by: viaVerio will pay you up to $1,000 for every account that you consolidate with us. http://ad.doubleclick.net/clk;4749864;7604308;v? http://www.viaverio.com/consolidator/osdn.cfm _______________________________________________ Tapestry-developer mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/tapestry-developer
