On Tue, Oct 5, 2010 at 8:47 AM, Ed <post2edb...@gmail.com> wrote: > > There are really two apps running in this case. First, there is the one > > created by JUnitShell, which contacts an RPC servlet to manage running > the > > test. The timeout you see is because that servlet didn't get contacted. > > Could you please give me some more info and pointers here? > I find the GWT Junit code difficult to follow, especially debugging is > a bit hard. > Where and how does this required servlet get contacted to overcome the > timeout? > If I follow the service method in GWTShellServlet, I don't understand > where the required contact is made. > And I can't find the relation with the messageQueue in the method > JUnitShell.notdone() that must contain the required info to overcome > the timeout exception :( >
Look at the comment at the top of JUnitShell -- it explains the connections. > > If you need a real browser to run the test in an automated way, the > recommendation would be to use -runStyle Selenium:uri and run a > Selenium-RC > > I also use Selenium, have about 2500 tests that run through Selenium, > that take about 50 hours to complete ;)... > Some background info: > I don't use runstyle for this. I run the tests against production > ready code produced during the nigtly build. > I run my tests through testNG with Maven surefire plugin. > Right, but there your Selenium tests are exercising the running app. I am suggesting it can also be used for running GWTTestCases in a real browser automatically. -- John A. Tamplin Software Engineer (GWT), Google -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
