To proof that Selenium does disrupt application execution I've modified the application so that it sends messages to the server in 1000ms intervalls. Those messages should get logged in the webserver log.
Now if I open the deployed application messages appear in the log as expected. If I then fire up the Selenium tests on the very same application no such messages end up on the server! I haven't found any info whether this happened to other people as well. But I'm asking again: Has anybody had similar issues? And maybe a solution? Thanks, -Stefan [email protected] (Stefan Hübner) writes: > Hi, > > We have a problem with testing a GWT (Google Web Toolkit) based > application. The application has different dialogs which get > attached/unattached to the DOM due to user navigation. > > Now the problem is, when running Selenium RC test (using the Selenium > Client Java Driver and Selenium server 1.0-beta-2) the app gets stuck > while Selenium tests wait for elements to become present. We use > isElementPresent() via the provided Wait class as recommended in the > Selenium-Wiki FAQ. It seems Selenium blocks the normal javascript > execution of the application, since the elements to wait for never show > up and it's waiting forever. Under normal circumstances attaching these > elements is a snap (a matter of milliseconds). > > This is a serious issue since it brakes all our tests. How could I get > around this behaviour? > > Thanks, > -Stefan > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
