> > I spent most of today trying to understand Selenium. I assume we want to > use Selenium 2 (WebDriver)? >
Yes, we do ;-) The Marmotinni source has build files that set up the test environment. > I started porting the Mustella AS test steps to Java and ran into an > interesting problem: Mustella generally waits for events before continuing > on to the next step, but I don't see any way to wait for events in > Selenium. > >From what I remember, you can so something like that using "WebDriverEventListener" and related classes. One implementation is demonstrated here [1]. More examples should be available through your local Google outlet ;-) I thought about requiring that the test apps inject code into the Goog > events to record the last event it dispatched. I also thought about > modifying Mustella so it waits for the same kinds of things that Selenium > knows to wait for, which seems to be restricted to changes to the UI. > I wouldn't change Mustella and I'd rather not mess with the event system to test the even system... If you provide a use case for the type of events you can't get Selenium to wait for/respond to, I can hack away a bit to see if a different set of eyes maybe see a working solution. EdB 1: http://www.qualitytesting.info/profiles/blogs/best-way-to-produce-good-logs-in-selenium-webdriver -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
