Component test assets refer to the test suites, test cases, test runs, stubs and other elements as displayed in the Test Navigator and the Package Explorer. Each type of test asset has its own properties and uses.
The Test Navigator lets you manipulate the execution-related elements of the test project.
Name | Icon | Located in | Description |
---|---|---|---|
Test project | ![]() |
Workspace | The test project contains all the test assets: test suites, test cases, stubs and test run results. The test project does not contain the components under test; these are located in their own development project. |
Test Suite folder | ![]() |
Test project | This folder contains all the test suites in your test project. |
Test suite | ![]() |
Test Suite folder | A test suite contains a set of individual test cases and deployment information. |
Test case | ![]() |
Test suite | A test case defines test behavior and test data. Each test case is mapped to a method in the test behavior script and to a test data table. |
Run folder | ![]() |
Test project | This folder contains all the test execution results from your test suites. |
Test run file | ![]() |
Run folder | This is the file that contains the test execution results. The file name is the name of the launch configuration with the execution date in the format YYYYMMDD_HHMM. |
Test suite run | ![]() |
Test run file | A test suite run is the result of the execution of a test suite. A test suite run is associated with a verdict for the test suite (Passed, Failed, Inconclusive, or Error). |
Test case run | ![]() |
Test suite run | A test case run is the result of the execution of a test case. A test case run is associated with a verdict. |
Data set run | ![]() |
Test case run | A data set run is the result of the execution of a data set or equivalence class. A data set run is associated with a verdict and test data. |
Individual test | ![]() |
Test data | An individual test run is produced for each element of a set or range within a data set. An individual test run is associated with a verdict and test data. By default, the first individual test run is automatically opened after the execution. |
The Package Explorer lets you manipulate the code-related elements of the test project.
Name | Icon | Located in | Description |
---|---|---|---|
Test project | ![]() |
Workspace | The test project contains all your test assets for a particular component under test. |
Behavior folder | ![]() |
Test project | This folder contains the component test behavior scripts for all of the test suites. |
Test package | ![]() |
Behavior folder | The test package contains test behavior scripts. |
Test behavior script | ![]() |
Test package | The test behavior script is a .java source file. |
Test class | ![]() |
Test project | The test class is derived from the JUnit TestCase class. There is typically one test class for each test suite. |
Test methods | ![]() |
Test class | Test methods are mapped to test cases. They describe the behavior of the test. |
Stub folder | ![]() |
Test project | This folder contains source files for stub components. |
Stub package | ![]() |
Stub folder | The stub package contains stub components. |
Stub components | ![]() |
Stub package | Stub component files specify the behavior of a stub. |