mvn clean verify
Executing Tests |
Previous | Next | Contents |
The Security TCK uses the JavaTest harness to execute a set of tests in the test suite. For detailed instructions that explain how to run and use JavaTest, see the JavaTest User’s Guide and Reference in the documentation bundle.
This chapter includes the following topics:
Note
|
The instructions in this chapter assume that you have installed and configured your test environment as described in Chapter 3, "Installation," and Chapter 4, "Setup and Configuration,", respectively. |
It is recommended to run the Security TCK from the command line in your shell environment
Note
|
The |
Start the tests using the following command:
mvn clean verify
To run the Security TCK signature tests, enter the following commands:
cd tck/signaturetest/
mvn clean verify
To run the Javatests:
cd tck/security-tck/
mvn clean verify
Use the following modes to run a subset of the tests:
Some test scenarios are designed to ensure that the configuration and deployment of all the prebuilt Security TCK tests against one Compatible Implementation are successful operating with other compatible implementations, and that the TCK is ready for compatibility testing against the Vendor and Compatible Implementations.
Verify that you have followed the configuration instructions in Section 4.1, "Configuring Your Environment to Run the TCK Against the Compatible Implementation."
If required, verify that you have completed the steps in Section 4.3.2, "Deploying the Prebuilt Archives."
Run the tests, as described in Section 5.1, "Starting JavaTest," and, if desired, Section 5.2, "Running a Subset of the Tests."
This test scenario is one of the compatibility test phases that all Vendors must pass.
Verify that you have followed the configuration instructions in Section 4.2, "Configuring Your Environment to Repackage and Run the TCK Against the Vendor Implementation."
If required, verify that you have completed the steps in Section 4.3.3, "Deploying the Test Applications Against the Vendor Implementation."
Run the tests, as described in Section 5.1, "Starting JavaTest," and, if desired, Section 5.2, "Running a Subset of the Tests."
A set of report files is created for every test run. These report files can be found in the report directory you specify. After a test run is completed, the JavaTest harness writes HTML reports for the test run. You can view these files in the JavaTest ReportBrowser when running in GUI mode, or in the web browser of your choice outside the JavaTest interface.
To see all of the HTML report files, enter the URL of the report.html
file. This file is the root file that links to all of the other HTML
reports.
The JavaTest harness also creates a summary.txt
file in the report
directory that you can open in any text editor. The summary.txt
file
contains a list of all tests that were run, their test results, and
their status messages.
Use the following modes to create test reports:
Specify where you want to create the test report.
To specify the report directory from the command line at runtime, use:
ant -Dreport.dir="report_dir"
Reports are written for the last test run to the directory you specify.
To specify the default report directory, set the report.dir
property in <TS_HOME>/bin/ts.jte
.
For example:
report.dir="/home/josephine/reports"
To disable reporting, set the report.dir
property to "none"
,
either on the command line or in <TS_HOME>/bin/ts.jte
.
For example:
ant -Dreport.dir="none"
Use the following modes to view an existing test report:
Use the Web browser of your choice to view the report.html
file in the
report directory you specified from the command line or in <TS_HOME>/bin/ts.jte
.
Previous | Next | Contents |