The following link explains how to set the timeout for an individual JUnit test case--however, this mechanism requires jdk1.5 or higher:

http://www.instrumentalservices.com/content/view/45/52/#_Timing_out_a_test

In addition, if you run JUnit tests under ant, you can use the timeout attribute of the <junit> task. Do we have a timeout mechanism for the current, home-grown test harness?

Mike Matrigali wrote:

While running derbyall my run hung all night on a junit test,
I assume this is expected if the test hung.


Reply via email to