Skip to main content

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

FieldDescription
DateThe date and time of execution.
Host nameThe machine on which the tests ran.
Submitted byThe user who started the run. If no separate submitting user is recorded, this field shows the executing user.
Executed byThe user under whose account the tests ran. Shown only when a separate submitting user is recorded.
Overall test resultThe 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

SectionContents
Overall test resultThe overall run result, color-coded. When the run was aborted, it also names the user who aborted it.
Table of contentsA linked entry for each test that was not aborted and did not return Not available.
Test summary gridOne row per test, listing the test, its status, and any failure cause.
Per-test detailsThe 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

SectionContents
System detailsOperating system, computer and hardware information, memory, video adapters, physical disks, printer drivers, antivirus status, time synchronization, and time-related permissions.
Summary of changesChanges detected since the last System report execution.
Software applicationsThe installed applications and their versions.
UpdatesThe 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

ItemDescription
Software application detailsThe component the report covers.
File report summaryVerification result for the component's files.
GAC file report summaryVerification result for global assembly cache files.
Files registration report summaryVerification result for registered files.
Registry report summaryVerification result for registry entries.
Installed filesEach 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

ItemDescription
Execution detailsDate and time, host name, submitting user, optional executing user, and overall test result.
Product name and versionThe product verified, where available.
Authentication configurationThe authentication provider in use: Internal, Domain, or ECM.
Test users and rolesThe accounts and roles exercised by the test.
Test procedure and stepsEach 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

ItemDescription
Execution detailsDate and time, host name, submitting user, optional executing user, and overall test result.
Test product and versionThe storage backend verified: Local File System, Content Management, OpenLab ECM, or Secure Storage.
Product configurationStorage type, authentication provider, and whether activity logs are on.
Test users and rolesThe accounts and roles exercised by the test.
Test configuration detailsThe 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 stepsEach step with its status.
Activity log checksThe 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

ItemDescription
Execution detailsDate and time, host name, local system type, submitting user, optional executing user, and overall test result.
OverviewThe kind of communication the local system verifies.
Connection to instrumentsWhen instrument connectivity applies: each instrument's name, location, type, connection status, and test status.
Connection to AICsWhen network connectivity applies: the connection result for each AIC.
DetailsAdditional 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

ReportContents
Workflow Test reportExecution 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 ReportThe 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​

Last updated: