Test report contents
Test Services produces a Summary report for every run that completes or is aborted. Depending on the tests and their results, the run can also produce no detailed report, one detailed report, or multiple detailed reports for a test. This page lists the fields and sections in the reports that are produced.
Common report header
The Test Services-generated Summary, System, Security, Storage, Connectivity, and Workflow reports open with a header that identifies the run. Submitted by is always shown. Executed by is shown when a separate submitting user is recorded.
Table: Common report header fields
| Field | Description |
|---|---|
| Date | The date and time of execution. |
| Host name | The machine on which the tests ran. |
| Submitted by | The user who started the run. If no separate submitting user is recorded, this field shows the executing user. |
| Executed by | The user under whose account the tests ran. Shown only when a separate submitting user is recorded. |
| 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 that was not aborted and did not return Not available. |
| Test summary grid | One row per test, listing the test, its status, and any failure cause. |
| Per-test details | The report-specific result content supplied by each test. |
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 | Operating system, computer and hardware information, memory, video adapters, physical disks, printer drivers, antivirus status, time synchronization, and time-related permissions. |
| Summary of changes | Changes detected since the last System report execution. |
| Software applications | The installed applications and their versions. |
| Updates | The installed patches and updates. |
OpenLab Software Installation Verification Test report
The Software Installation Verification Test (SVT) produces reports for the software components it verifies. A product marked Skipped has no generated product report. See Software Installation Verification Test for how to verify skipped products.
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 |
|---|---|
| Execution details | Date and time, host name, submitting user, optional executing user, and overall test result. |
| 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. |
| Test procedure and steps | Each test procedure step with its status. |
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 | Date and time, host name, submitting user, optional executing user, and overall test result. |
| Test product and version | The storage backend verified: Local File System, Content Management, 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 uses one consolidated report format for instrument and network connectivity. The sections in a particular report depend on the local system type and the connections that apply there.
Table: Connectivity Test report contents
| Item | Description |
|---|---|
| Execution details | Date and time, host name, local system type, submitting user, optional executing user, and overall test result. |
| Overview | The kind of communication the local system verifies. |
| Connection to instruments | When instrument connectivity applies: each instrument's name, location, type, connection status, and test status. |
| Connection to AICs | When network connectivity applies: the connection result for each AIC. |
| Details | Additional network-connection details when the report provides them. |
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 | Execution details, the OpenLab CDS product and version, and each Test Services workflow step with its status, including the activity-log and audit-trail entries checked. |
| Algorithm Evaluation Report | The evaluation of each algorithm verified by the CDS acquisition, with its expected result, observed result, and status. |
The run's Summary report contains a separate Workflow Test summary. It states whether the workflow completed without errors and whether the required activity-log and audit-trail entries were found; it is not an algorithm-by-algorithm summary of the Algorithm Evaluation 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.
Last updated: