test command
template A generalized specification of a test command in a test environment. The test command is specified in the test environment using variables so that it can execute any test in the test suite regardless of its arguments.
test description
test environment One or more test command templates that the test script uses to execute tests and a set of
test execution model The steps involved in executing the tests in a test suite. The test execution model is implemented by the test script.
test finder When using the JavaTest harness, a nominated class, or set of classes, that read, verify, and process the files that contain test descriptions in a test suite. All test descriptions that are located are handed off to the JavaTest harness for further processing.
test framework Software designed and implemented to customize a test harness for a particular test environment. In many cases, test framework components must be provided by the TCK user. In addition to the test harness, a test framework might (or might not) include items such as a: configuration interview, Java Application Manager (JAM), test agent, test finder, test script, and so forth. A test framework might also include other
test harness The applications and tools that are used for test execution and test suite management. The JavaTest harness is an example of a test harness.
test script A Java technology software class whose job it is to interpret the test description values, run the tests, and report the results back to the JavaTest harness. The test script must understand how to interpret the test description information returned to it by the test finder.
test specification A
test suite A collection of tests, used with the test harness to verify compliance of the technology implementation to a Java specification. Every Technology Compatibility Kit (TCK) contains one or more test suites.
Glossary 105