Hi all, We've been using Selenium TestRunner for some time and are now looking into migrating to the driven mode since writing those HTML tests really isn't that delightful.
Now we're in a point where we have a JUnit test suite that deploys our application on Tomcat (launched with Selenium's OutbeddedTomcat class), launches Mozilla (on Linux), and manages to access the front page (login page) of the application as well as actually log in. The problem is that after executing the Selenese command "|clickAndWait|submitLogin||", the next "|verifyTextPresent|Foo||" always fails even though we can clearly see the text "Foo" in Selenium's browser frame. I hacked a couple of System.out.println's into the Selenium driver (we're using Java as you may have guessed from us deploying on Tomcat) and found out that the server is responding with "HTTP 500 Internal Server Error" when the test polls the URL "http://localhost:8080/selenium-driver/driver?commandRequest=|verifyTextPresent|Foo||" So, my question is how to go about debugging what's happening on the server side? -Lasse- PS. I also got an HTTP 500 when trying the "pause" command so we're now sleeping with Thread.sleep() in order to let the application process requests etc. _______________________________________________ Selenium-users mailing list Selenium-users@lists.public.thoughtworks.org http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users
