You can run unit test methods from:
The Class Browser, by selecting a unit test class or method and then pressing the F9 key or by selecting the Unit Test command from the Jade menu. (To run unit tests in debug mode, press SHIFT+F9 or select the Unit Test Debug command from the Jade menu.)
The Schema Browser, by selecting a schema that has a unit test class and then pressing the F9 key or by selecting the Unit Test command from the Jade menu. (To run unit tests in debug mode, press SHIFT+F9 or select the Unit Test Debug command from the Jade menu.)
A batch of tests, using a RootSchema application provided for that purpose.
Code, by using the
Running unit tests from code is considered the exceptional case. You would consider doing this only if you want more control over the presentation of the test results.
The name of the JADE unit testing application is JadeUnitTest and that of the batch version is JadeUnitTestRun. It may be necessary to change your
When the unit tests finish running, the final failure count reflects the following.
If a class instance create fails, the first class method executed will be counted as failed.
If a unitTestBeforeClass method fails, the first class method executed will be counted as failed.
If a unitTestAfterClass method fails, the last class method executed will be counted as failed.
Any failure associated with a method will count as a failure only in the final failure statistics, whether it is a failure resulting from any of the previous items in this list or from a failure in the unitTestBefore, unitTestAfter, or unitTest method.
The total failures displayed while the tests are running shows the actual number of methods that failed. This figure is replaced on completion of the test run by the combined figure of each of the list items in the previous list.