On Wed, Oct 20, 2010 at 9:22 AM, Ed <[email protected]> wrote: > I couldn't hold back investigating a bit more. > Like described in my last post, the timeout" always" occurred/started > in a GWTTestCase class that contained two test cases that involve RPC > calls. > > I did split up these test cases such that they have their own > GWTTestCase class, and the timeout appearantly disappeared as I have > seen it now for a week. All tests run fine now. > > Any idea how/why this is ? > After all the debugging/work I get the feeling that there exists some > "deep hidden bug" causing this timeout. .. >
It's hard to say what the problem is without seeing your code, but take a look at GWT's ValueTypeTest for an example that does very many RPCs in one test class. The important things are: - call delayTestFinish before making the async call - in all cases of the result, make sure to fail the test in some way or call finishTest -- John A. Tamplin Software Engineer (GWT), Google -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
