Introduction to Test Services
Test Services is Agilent's browser-based application for verifying that an OpenLab CDS deployment works. It is built as a general verification framework. Its core tests check the underlying OpenLab platform that OpenLab CDS runs on. An OpenLab CDS plug-in adds the tests that are specific to OpenLab CDS. It gives you a simple, automated way to confirm that the software and the system it runs on are operating as intended. It also produces a report you can keep as evidence. This page introduces what Test Services does and points you to the rest of the documentation.
Test Services is installed automatically with OpenLab CDS and runs on every machine in the deployment. You can open it from any machine in your lab using a web browser. It is intended for two audiences. Lab users run verification tests and review the results. Administrators install, license, and configure the application.
What Test Services verifies
Test Services presents a set of tests that each confirm a different aspect of the deployment. Some tests check the installed software, others check the storage system, the security configuration, instrument connectivity, or a full data-acquisition workflow. You select the tests you want, run them, and Test Services reports whether each one passed.
Most of these checks are not specific to OpenLab CDS. The core framework tests are the System Report, the Software Installation Verification Test, the OpenLab Security Test, and the OpenLab Storage System Test. They verify the shared OpenLab platform that OpenLab CDS is built on. That platform includes OpenLab Shared Services authentication and access control, the storage system, the integrity of the installed Agilent software, and the operating system. Because they target the platform rather than CDS itself, the same framework can verify other Agilent applications built on it. The OpenLab CDS plug-in adds the two CDS-specific tests, the Connectivity Test and the Workflow Test.
The tests available on a machine depend on the machine's role in the deployment and on which plug-ins and licenses are installed. Test Services shows only the tests that apply to the machine you are using. For the full list of tests and where each one runs, see Available tests.
How the results are presented
Each run produces a Summary report that states one overall result and links to the individual report for each test. The overall result is conservative: every test must pass for the run to pass. A passing Summary report is therefore a strong statement about the deployment. For how the result is determined, see About the Summary report.
Licensing in brief
You do not need a license to log in, to run the System Report, the Software Installation Verification Test, or the Connectivity Test, or to view past results. The Security Test, Storage System Test, and Workflow Test require a license. All applicable licenses are included with OpenLab CDS Workstation Plus systems; for other CDS products, licenses are purchased and installed separately. For details, see About licensing.
How this documentation is organized
The documentation follows the task you are trying to complete:
- Tutorials. A guided lesson that takes you through a first verification from end to end. Start with Get started with Test Services.
- How-to guides. Short procedures for specific tasks, such as Run verification tests and Manage licenses.
- Concepts. Background that explains how Test Services works and why, including How Test Services works and System types and recommended tests.
- Reference. Look-up material such as Available tests, Roles and privileges, and the Glossary.
- Troubleshooting. Diagnostic guides for when a run does not behave as expected, such as Results reported as not passed.
Within the application, the documentation menu on the home page links to the Test Services User Guide and the Administration Guide. You can open or download these as PDFs in the application's language.
See also
- Get started with Test Services: run your first verification from end to end.
- How Test Services works: the deployment model and the test framework.
- Available tests: every test and where it runs.
- Log in to Test Services: open the application and log in.