TABLE
TABLE C-1 Framework Test Description Fields
Field | Description |
|
|
title | A descriptive string that identifies what the test does. The title appears in |
| reports and in the harness status window. |
source | For compiler tests, contains the names of the files that are compiled |
| during the test run. |
| For runtime tests, contains the names of the files previously compiled to |
| create the test’s class files. Precompiled class files are included with the |
| test suite. Source files are included for reference only. Source files are often |
| .java files, but can also be .jasm or .jcod files. |
| • .jasm is a |
| containing sets of bytecodes that are unusual or invalid for use in |
| runtime tests. |
| • .jcod is a |
| invalid structure for use in runtime tests. |
| These tools are used to generate class files that cannot be reliably |
| generated by a Java programming language compiler. |
| For most XML parser tests in the test |
| contains the names of the files that are processed during the test run. |
| These files are XML schema sources and XML documents usually having |
| file name extensions of .xsd and .xml respectively. Such tests share a |
| single precompiled class, TestRun, that invokes the XML parser under |
| test through the Java technology API and passes the source file names to |
| the parser for processing. |
| The test model is similar to compiler testing because the sources used in |
| the tests contain valid and invalid use of various constructs of |
| corresponding languages. |
keywords | String tokens that can be associated with a given test. They describe |
| attributes or characteristics of the test (for example, how to execute the |
| test, and whether it is a positive or negative test). Keywords are often |
| used to select or deselect tests from a test run. See “Keywords” on page |
| 94. |
executeClass | The main test class that the harness loads and runs. This class might in |
| turn load other classes when the test is run. |
|
|
