Tuesday, October 8, 2013

Re: delayTestFinish() from GWTTestCase not working in pure java tests


On Tuesday, October 8, 2013 5:08:04 PM UTC+2, Derek Thurn wrote:
I'm trying to verify that some JavaScript code behaves identically to an existing Java library. I've created some tests that subclass GWTTestCase to check this. Unfortunately, when I try and do the pure-java test in development mode (by returning null for the module name, as the documentation suggests), the methods like delayTestFinish() don't appear to work. Tests just finish as soon as the test method exits. Is this the intended behavior? If so, has anybody made a pure-java implementation of GWTTestCase so test logic can be shared between client and server code?

For now at least, yes, this is the intended behavior. The RequestFactory tests in GWT use JRE and GWT tests from the same base code (using delayTestFinish), but JRE tests use the InProcessRequestTransport (or UrlRequestTransport) which is blocking.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]

<< Home


Real Estate