Failed. Unexpected exit from test
Answer: The test has completed in an unexpected manner.
This could be caused by some sort of fault (e.g. a segmentation fault)
or because the harness has detected a call to System.exit
from the test.
Tests are not allowed to call System.exit
because the
test must have the ability to run in the same JVM as the harness.
Calling System.exit
while the test is running in this
manner whould cause the harness itself to exit! Instead of calling
System.exit()
, throw an exception.
Be warned that the AWT event thread does not propagate exceptions,
so if the test was exiting from the event thread, it is not sufficient
to simply throw an exception. The test must set some variable which
can be used to throw an exception from one of the methods called by
the harness. (i.e. init()
, start()
,
stop()
, or destroy()
)