Running Unit Tests

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 runTests method of the JadeTestRunner class or by displaying the Unit Test Runner form.

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 getAndValidateUser method to enable the unit testing applications to run.

By default, Jade initializes packages for RootSchema applications running in user schemas, including unit tests run using the Jade Unit Test framework. If you want to disable this initialization when the server node or the client node starts the application, define the PackageInitializationDisabledApp<n> parameter in the [JadeClient] section of the Jade initialization file. You can disable package initialization if the unit tests do not require functionality from any package imported by the user schema. This can reduce the startup time for the tests.

For example, to disable package initialization for unit tests run by the GUI JadeUnitTest application, add the following to your Jade initialization file.

[JadeClient]
PackageInitializationDisabledApp1=UnitTestSchema,JadeUnitTest

For example, to disable package initialization for unit tests run by the batch JadeUnitTestRun application, add the following to your Jade initialization file.

[JadeClient]
PackageInitializationDisabledApp1=UnitTestSchema,JadeUnitTestRun

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.