OpenLab Software Installation Verification Test
The OpenLab Software Installation Verification Test confirms that the Agilent software on a machine is installed correctly and has not been altered. It checks the files of every registered Agilent product against the expected set, so you can show that what is running on the computer matches what Agilent shipped. The test runs on every deployment type and needs only the Test Services User role.
What the test verifies
The verification is performed by the Software Verification Tool (SVT), a separate Agilent utility installed alongside OpenLab CDS. Test Services discovers each installed Agilent product, then has the tool qualify that product's files: it confirms the files are present, in the right place, and match the recorded version and checksum. The result is one report per product rather than a single combined pass, which lets a reviewer see exactly which component was checked.
Each per-product report describes the application and summarizes the file checks it ran, covering installed files, global assembly cache entries, file registration, and registry entries, and it lists every installed file with its full path and version. The report is a record of the qualified installation, useful both as routine evidence and as a starting point when a component looks wrong.
Because the test only verifies what the tool can find, it depends on each product being correctly registered with the tool. If the Software Verification Tool itself is not installed, the test is disabled and reports that no tool is available, rather than showing a technical error.
When verification can fail
The test passes only when every registered product passes its file checks. A single product with a missing file, a wrong version, or a checksum mismatch makes the whole test fail. This is deliberate: the test exists to detect exactly that kind of drift.
One reason a previously passing test starts to fail is a software change that left the file registration out of step with the installed files. Installing or removing an Agilent patch, or upgrading OpenLab CDS, can leave the registered reference set pointing at the old files until it is brought back into line. When this happens the test reports the affected product as failed; restoring the correct registration returns the test to passing. Resolving registration problems is an administrator task, so contact your administrator or Agilent support if a product fails verification after a software change.
Where it fits
The Software Installation Verification Test runs on its own and does not require a license. Its per-product reports are stored with the other reports in the OpenLab storage backend, included in the overall Summary report, and available from the home page and the execution history. For the steps to run any test, see Run verification tests.
See also
- Run verification tests: select and start a test.
- Available tests: which tests run on each deployment type.
- Test result statuses: what each result value means.
- About the Summary report: how individual results roll up.