Ok, after some more digging I think I've figured out why this is happening (the symptom anyway). The workaround is to just compile your app with the OBF style before running your test instead of using PRETTY or DETAILED. For more gory details, read on.
Selenium wraps the 4-parameter 'window.open' call in their own implementation so that they can keep track of open windows. Gwt's rpc code: (RequestBuilder:381, XMLHTTPRequest:186) registers their own method called 'open' as a wrapper of XMLHTTPRequest's open, but they do so in the 'window' context. When selenium hooks in to the gwt app, it puts its wrapper around gwt's 'open' method (even though its not a real window.open call). When the rpc call is made, mayhem ensues since there really is no window opening at all. I think the error could be fixed on either side, but I'm going to log a gwt issue since the method named 'open' in the 'window' context probably shouldn't be overridden unless absolutely necessary. On Jul 21, 12:11 pm, David <[EMAIL PROTECTED]> wrote: > I have some Selenium tests that were working under mygwt/Gwt1.4 that > are now broken with the only change being to upgrade to GXT 1.0 andGWT1.5RC1. > I am getting a > (TypeError):openedWindowhasnopropertiesfileName:http://localhost:8080/selenium-server/core/scripts/selenium-browserbo... > lineNumber: 557 > > This is occuring during aGWTRPC call. It appears the failure > happens Anybody here have selenium tests working with GXT1.0 usingGWT'sRPC > calls? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
