It's a neat idea. How would you avoid specific dependencies between UiBinder and Selenium? If you're looking to introduce hooks into the UiBinder parsing and code generation process, I don't think we're ready for that yet. The current api at that level is a mess and we need to be able to tidy it up, something that is unlikely to happen in the 2.0 time frame.
On Sun, Sep 20, 2009 at 5:50 PM, John Tamplin <j...@google.com> wrote: > On Sat, Sep 19, 2009 at 7:50 PM, Sripathi Krishnan < > sripathi.krish...@gmail.com> wrote: > >> Also, I read a few days ago that the GWT team were working on a HtmlUnit >> based testing methodology, and I was not sure if the above approach would >> become useless once that got released. >> > > HtmlUnit will primarily replace the use of the existing embedded browser -- > to test things that require a real browser (such as layout, or places where > HtmlUnit provides inaccurate emulation), you would need to use Selenium (and > you could use it either in web mode, which requires a JS compile, or in > development mode, which would require arranging for the Selenium browser to > have a plugin (and for FireFox, in the appropriate profile). > > So work spent on improving Selenium integration will not be wasted on > account of HtmlUnit work (not sure about WebDriver). > > -- > John A. Tamplin > Software Engineer (GWT), Google > > > > > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
