Rick Hillegas wrote:
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
I must admit that JUnit4 seems to have several nice features I would
very much like to use :)
Too bad I must probably wait for years (1.4 EOL) before I can do that
wrt Derby!
--
Kristian
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.
