Skip to main content

OpenLab CDS Workflow Test

The OpenLab CDS Workflow Test confirms that OpenLab CDS produces correct results across a complete chromatography workflow. It drives a real run end to end, from acquisition through data analysis to reporting, using reference data with known outcomes, and then checks that the software's calculations match those outcomes. It is the test that exercises CDS itself rather than the surrounding system, so it runs where acquisition lives: on an AIC, a Workstation, or a Workstation Plus. The test is contributed by the OpenLab CDS plug-in.

What the test verifies​

The test sets up a project and a virtual instrument, submits a sequence built from Agilent reference files, lets it run, and then evaluates the results. The reference files, including the report templates, sequences, and acquisition and processing methods, are deployed with Test Services and kept valid for the installed version of OpenLab CDS, so the test always has a known-good baseline to compare against.

What it is verifying is the correctness of the CDS algorithms along the workflow. Because the input data is fixed and the expected results are known, any difference between the computed results and the reference values points to a problem in the software rather than in the sample. The test reports verifications, not validations, of acquisition, data analysis, and reporting.

The test also confirms that the workflow is fully traceable. As the sequence runs, the test can edit it, for example changing a sample's custom parameter or its acquisition method, and each such change is recorded with a reason. After the run, the test verifies the CDS sequence audit trail, checking that every expected entry is present. If an expected audit entry is missing, the test fails, because an unrecorded change is as much a defect as a wrong calculation in a regulated workflow.

Where it applies​

The test is available only where OpenLab CDS acquisition is present and the installed CDS version meets the minimum for your Test Services release. It is not shown on Server machines, and on a Client it appears but cannot run because there is no acquisition software. When the test is available, its entry shows the installed CDS version; when it is not, the test explains the reason, such as that a newer CDS version is required or that the machine is not an instrument controller.

Why it needs a license and privileges​

The Workflow Test requires the CDS Workflow license (see Licensing). The license is acquired at the first execution and is not returned to the pool afterward, so each machine that runs the test consumes one. On Workstation Plus the license is included; on other products it is purchased and installed separately. If no license is available, the test fails at the license-check step, labelled Checking for license 'QlaCDSWorkflow'.

The running user must hold the OpenLab CDS privileges that the test needs. These let the test manage the instrument and location, run the instrument, create and modify the sequence, edit a running sequence, and view the activity log. ECM backends require a few additional content permissions. The test checks these privileges before it starts, so a missing privilege is reported up front rather than partway through the run.

Where it fits​

The Workflow Test produces a dedicated workflow report and an algorithm-evaluation report, and a summary of the algorithm evaluation is included in the overall Summary report. The reports are stored with the other reports in the OpenLab storage backend and available from the home page and the execution history. For the steps to run any test, see Run verification tests.

See also​