Not sure if its worth opening a bug for it but I noticed that JUnitShell somehow causes ugly connection refused messages in the browser's console for the last test in a GWTTestCase if running in prod mode and with runStyle manual. However I have verified that the tests itself execute correctly and JUnit correctly picks up succeeded and failed tests.
After talking with Colin on IRC a bit we think it is likely that the upgrade from jetty6 to jetty8 might have caused this behavior. It looks like that the GWT-RPC connection for the last test method will be closed without sending a HTTP 200 back to the browser which causes quite some ugly errors in the browser's log. For a GWTTestCase with three test methods the console shows: <https://lh3.googleusercontent.com/-0tMq26z9g4A/UyIqGsb267I/AAAAAAAAAHY/FZ6JjJw2vWc/s1600/console.png> First request is for client infos and request 2-4 are the test results of the three methods. From the browser's point of view the last test result could not be send back and thus GWT will retry three times before giving up. The first time I saw this I was wondering if I should trust the actual JUnit results or not, so it is maybe worth a bug entry. -- J. -- http://groups.google.com/group/Google-Web-Toolkit-Contributors --- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
