So ... you have things happening that take longer than 30 seconds on your box? What are you running on; nothing should take that long!
Generally, the timing issues occur for me when the test gets something wrong while waiting for an Ajax operation to complete. On Wed, Oct 26, 2011 at 3:28 AM, Massimo Lusetti <[email protected]> wrote: > I'm actually not sure about a solution but... Here the tests, > especially the integration ones, are too sensible to timing and when > my box is busy (almost always) I end up with failing tests such as > this one: > > com.thoughtworks.selenium.SeleniumException: Timed out after 30000ms > at > com.thoughtworks.selenium.HttpCommandProcessor.throwAssertionFailureExceptionOrError(HttpCommandProcessor.java:101) > at > com.thoughtworks.selenium.HttpCommandProcessor.doCommand(HttpCommandProcessor.java:95) > at > org.apache.tapestry5.test.ErrorReportingCommandProcessor.doCommand(ErrorReportingCommandProcessor.java:69) > at > com.thoughtworks.selenium.DefaultSelenium.open(DefaultSelenium.java:343) > at > org.apache.tapestry5.test.SeleniumTestCase.open(SeleniumTestCase.java:924) > ... > > What are your solutions about ? > > Thanks for any pointer besides "make the box more powerful or let it > to less work"... > -- > Massimo > http://meridio.blogspot.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
