Mário Lopes wrote: >unit tests to simulate the interaction between them and the user. > >For instance, InlineEditBox. Suppose the following action: the user >selects component, he changes the content to something that's not >acceptable and a message would be shown. How can I build test cases to >simulate this actions? > > I would suggest selenium tests for such stuff, at http://www.openqa.org/selenium/ . They're much more easily programmed - and you can see what works and what breaks in different browsers. We use them in tacos, if you have the demo installed, navigate to http://localhost/selenium or see it at http://demo.opennotion.com/tacos4/selenium/
> I've seen those files but I don't see any reference to them on any > >files so I don't know where to put them. > > In tacos demo app, the Border component includes the SiteMap... see http://svn.sourceforge.net/viewcvs.cgi/tacos/trunk/demo/docroot/WEB-INF/Border.html?view=log and http://svn.sourceforge.net/viewcvs.cgi/tacos/trunk/src/java/net/sf/tacos/components/SiteMap.html?view=log >Kind regards, > >-- Mário > > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642 _______________________________________________ Tacos-devel mailing list Tacos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tacos-devel
