## JUnit TestRunner Properties

The TestRunners use a properties file for preference settings. This file is stored in the folder referred to by the "user.home" system property. The following properties are supported:

loading | Use a custom class loader to load classes for each run. Default value=true.
filterstack | Filter JUnit internal methods in failure or error stack traces. Default value=true.
maxmessage | The maximum output length. Default value=500. Set maxmessage to -1 to disable output truncation. Disabling the output truncation will result in long test runs when an assertEquals method fails and the toString() method results in massive output.
TestCollectorClass Swing UI TestRunner only | The Swing TestRunner supports to browse test classes. There is an additional browse ("...") button besides the suite combo. It shows a simple dialog to select a test class from a list. Different strategies to locate Test classes are supported and you can plug-in your own strategy. This allows to leverage functionality provided by an extension API of an integrated development environment (IDE). To define a custom test collector you 1) implement the junit.runner.TestCollector interface and 2) add an entry to the junit.properties file with the key TestCollectorClass and the name of your TestCollector implementation class as the key: TestCollectorClass=junit.swingui.LoadingTestCollector This class has to be installed on the class path.
FailureViewClass Swing UI TestRunner only | Plug-in a custom failure panel that provides additional functionality like navigating from a failure to the source. To do so you implement the junit.runner.FailureDetailView interface and register the implementation class in the junit.properties file under the key FailureViewClass, for example. FailureViewClass=somepackage.MyFailureViewClassName. This class has to be installed on the class path.