Test report contents
Test Services produces a Summary report for every run and a separate report for each test that runs. This page lists the fields and sections each report contains. The reports a run produces depend on which tests ran; the Summary report is always generated when a run completes or is aborted.
Fields common to all reports
Every report opens with a header that identifies the run. The submitting and executing users are shown only when tests run under separate credentials.
Table: Common report header fields
| Field | Description |
|---|---|
| Host name | The machine on which the tests ran. |
| User | The user who ran the tests. |
| Date | The date and time of execution. |
| Submitted by | The user who started the run. Shown only when separate credentials are configured. |
| Executed by | The account under which the tests ran. Shown only when separate credentials are configured. |
| Overall test result | The overall result of the run: Passed, Failed, Aborted, or Not available. |
Summary report
The Summary report brings together the results of all tests run at a given date and time, with links to each individual report. For how the overall result is decided, see About the Summary report.
Table: Summary report sections
| Section | Contents |
|---|---|
| Overall test result | The overall run result, color-coded. When the run was aborted, it also names the user who aborted it. |
| Table of contents | A linked entry for each test in the run. |
| Test summary grid | One row per test, listing the test, its status, and any failure cause. |
| Per-test details | For each test: name, description, result, execution time, and links to that test's individual reports. |
System report
The System report lists version information for everything installed on the host and highlights changes since the previous System report.
Table: System report sections
| Section | Contents |
|---|---|
| System details | Identifying information for the host machine. |
| Software applications | The installed applications and their versions. |
| Updates | The installed patches and updates. |
| Summary of changes | Changes detected since the last System report execution. |
OpenLab Software Installation Verification Test report
A separate Software Installation Verification Test (SVT) report is generated for each OpenLab software component.
Table: SVT report contents
| Item | Description |
|---|---|
| Software application details | The component the report covers. |
| File report summary | Verification result for the component's files. |
| GAC file report summary | Verification result for global assembly cache files. |
| Files registration report summary | Verification result for registered files. |
| Registry report summary | Verification result for registry entries. |
| Installed files | Each installed file, with its full installation path and installed version. |
OpenLab Security Test report
The Security Test report records the results of the OpenLab Security Test. The test description differs depending on whether the system uses internal, domain, or ECM authentication.
Table: Security Test report contents
| Item | Description |
|---|---|
| Product name and version | The product verified, where available. |
| Authentication configuration | The authentication provider in use: Internal, Domain, or ECM. |
| Test users and roles | The accounts and roles exercised by the test. |
| Sub-test results | The result of each sub-test. |
OpenLab Storage System Test report
The Storage System Test report records the storage system verification.
Table: Storage System Test report contents
| Item | Description |
|---|---|
| Execution details | Time of execution, executing user, host name, and overall result. |
| Test product and version | The storage backend verified: Local File System, OpenLab ECM, or Secure Storage. |
| Product configuration | Storage type, authentication provider, and whether activity logs are on. |
| Test users and roles | The accounts and roles exercised by the test. |
| Test configuration details | The file search (Quick Search) sub-test included in the run, with its maximum wait time, or a note that it was not selected for the run. |
| Test procedure and steps | Each step with its status. |
| Activity log checks | The activity log entries verified, when activity logging is on. |
OpenLab CDS Connectivity Test report
The Connectivity Test report records the verification of communication between OpenLab components and instruments. It is a single consolidated report covering both instrument and network connectivity, and is generated only when the OpenLab CDS Connectivity Test runs.
OpenLab CDS Workflow Test reports
The Workflow Test produces two reports, generated only when the OpenLab CDS Workflow Test runs.
Table: Workflow Test reports
| Report | Contents |
|---|---|
| Workflow Test report | The verification of the CDS workflow across acquisition, data analysis, and reporting. |
| Algorithm Evaluation Report | The evaluation of each algorithm verified by the test, with expected result, observed result, and status. A summary of this report is also included in the Summary report. |
See also
- About the Summary report: what the Summary report is and how the overall result is decided.
- Test result statuses: the meaning of each result and status value.
- The System report test: what this test verifies.
- Test result locations: where the reports are stored.