To recap from another thread:
- When running a JUnit test using -remoteweb, there are error conditions where RunStyleRemoteWeb calls System.exit(1)
- This is not a problem when you run a test standalone, but when running as a junit ant task, these errors get reported somewhat cryptically as:
testcase: testGetBuildInfo took 0.002 sec
Caused an ERROR
Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
junit.framework.AssertionFailedError: Forked Java VM exited abnormally. Please note the time in the report does not reflect the time until the VM exit.
at java.lang.Thread.run(Thread.java:595)
Scott suggested we replace the System.exit(1) with throwing an exception. This change does that, plus adds a shutdown hook that will send a message to BrowserManagerServer to kill any browsers that are still running at the end of the test.
M user/src/com/google/gwt/junit/RunStyleRemoteWeb.java
--
Eric Z. Ayers - GWT Team - Atlanta, GA USA
http://code.google.com/webtoolkit/
Don't miss Google's biggest developer event of the year
http://code.google.com/events/io