Thanks for the response. With the '-runStyle Manual:1' option, GWT starts up, but then hangs and never outputs the URL to the console. I'd have to think about how to check the headers without being able to run the manual test. I'll ask someone else on the team to give it a shot.
It was working before... and I believe the change was GWT update. On Wednesday, December 17, 2014 5:13:37 PM UTC-6, Jens wrote: > > Hmm maybe the sessionId cookie gets lost somehow during the test? Can you > verify that the first request creates a session on the server and the > response contains a Set-Cookie header with the sessionId? Finally the > second request should send that sessionId cookie to the server otherwise a > new session will be created again. > > Does it work when you launch your GWT tests using the JVM parameter: > > -Dgwt.args="-prod -runStyle Manual:1" > > and then visit the provided URL in a browser? That basically compiles your > GWT test module to JavaScript and lets you execute the tests in a browser. > > -- J. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
