On Nov 27, 2:08 am, John Tamplin <[email protected]> wrote: > On Thu, Nov 26, 2009 at 12:34 PM, <[email protected]> wrote: > > Unfortunately, I have neither selenium nor RMI configured, and > > PopupPanel tests are disabled in HtmlUnit; so I haven't been able to run > > the unit tests against my changes; but I used them in a project (by > > overriding the files, just put them earlier in the classpath) and had > > the expected result (though obviously not everything changes I made had > > been "tested" this way). > > The easiest way to test with particular browsers (if you don't need to have > a test farm setup anyway) is to use -runStyle Manual and connect with > whatever browser you want to test. You can use -runStyle Manual:2 and test > two browsers simultaneously, etc.
Yes, that's what I usually do ...except for GWT itself, for which I try to only use the build.xml (to use the same classpath, JUnit arguments, etc. as your build system), and there's no such targets as test.manual, test.web.manual, test.hosted.manual, etc. in user/ build.xml ;-) (I also tried adding such test.manual targets, but it took an eternity for the "open this URL in a browser" line to appear so I gave up – t'was time to go home ;-) ) -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
