I found a bug related to opening Safari on Mac OS X in BrowserManagerServer - it opens the URL prefixed with the current path of my shell.
Anyway, found a way to fix that (see patch at Issue #4209). Q: Is the Selenium route 'just another way' to run the tests on a browser? I found some comments at this thread http://groups.google.com/group/google-web-toolkit-contributors/browse_thread/thread/15d9dbe395026532/f70b8122faa03c58?lnk=gst "Longer term, I think we need to do away with RemoteBrowserManager and replace it with Selenium. Current versions of Selenium-RC can launch Chrome and IE, so it seems better to use something that is actually supported and avoids the known problems with RemoteBrowserManager." Thanks, Bart Guijt E: bgu...@gmail.com T: +31 6 30408987 On 7 nov 2009, at 7 nov, 03:03, John Tamplin wrote: > You might also consider using -runStyle Selenium:connect-string > instead -- that way you can run a Selenium-RC server with the > browser you want rather than BrowserManagerServer. > > -- > John A. Tamplin > Software Engineer (GWT), Google > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
