System types and recommended tests
The tests Test Services offers on a machine, and the smaller set it recommends, depend on what that machine does in your OpenLab CDS deployment. This page explains why the lists differ, so you can tell at a glance whether a machine is showing what you expect. For the authoritative table of which test runs where, see Available tests.
Why availability depends on the machine
Each machine in an OpenLab CDS deployment has a role: it may be a Workstation or Workstation Plus, an OpenLab Server or ECM XT server, a client, or an Analytical Instrument Controller (AIC) that drives instruments. A test only makes sense where the thing it verifies is present. The Workflow Test, for example, drives an acquisition, so it runs where instruments are controlled (an AIC, a Workstation, or Workstation Plus) and does not appear on a server. A test contributed by a plug-in appears only where that plug-in is installed.
Test Services detects the machine's role and shows the tests that apply to it. A test that does not apply is never shown; a test that applies but is not part of the default set can still be displayed on request.
Recommended tests versus all tests
Within the tests that apply to a machine, Test Services marks a subset as recommended: the tests that best confirm a machine of that role is operating correctly. By default the home page shows only the recommended tests, with a message that you can choose to show all available tests instead. Showing all tests reveals the applicable tests that are not in the recommended set, grouped by category.
The recommended set is a starting point, not a restriction. You can run any applicable test on a machine, recommended or not. The default keeps the home page focused on the checks that matter most for that role.
How the recommended set varies by role
The emphasis shifts with what the machine is responsible for:
- OpenLab Server or ECM XT server. Verification centers on the platform itself: software integrity, the installed-software inventory, the security configuration, and storage. Acquisition and connectivity tests do not apply.
- AIC. Verification centers on instrument work: software integrity, the software inventory, the acquisition workflow, and instrument connectivity.
- Client. Similar to an AIC but without the local acquisition workflow: software integrity, the software inventory, and connectivity.
- Workstation Plus. A self-contained system, so its recommended set is broad: software integrity, the software inventory, the acquisition workflow, the security configuration, connectivity, and storage.
- Workstation. A standalone system with local file storage that also controls instruments, so its recommended set is broad: software integrity, the software inventory, the acquisition workflow, the security configuration, connectivity, and storage.
For the exact per-machine availability, including which tests need a license and which need the OpenLab CDS plug-in, see Available tests.
A test can be present in the product but hidden until it is ready for use. A hidden test does not appear in the recommended or all-tests views even where its machine role would otherwise include it.
See also
- Available tests: the full availability table by deployment type.
- How Test Services works: the deployment model behind these differences.
- The plug-in framework: how plug-ins add tests to a machine.
- Run verification tests: select recommended or all tests and start them.