Skip to main content

OpenLab Storage System Test

The OpenLab Storage System Test confirms that the storage system can store, secure, and maintain files and folders the way a regulated lab depends on. It performs real file and folder operations against the backend in use, then checks that the operations behaved correctly. Activity-log verification depends on the backend and its logging configuration. The test is recommended on Server, Workstation Plus, and Workstation systems; it can also be run on other deployment types, although it is not recommended there. It was formerly called the Data Integrity and Traceability Test.

What the test verifies​

The test acts on the actual storage backend, so what it checks depends on the storage system in use: the local file system on a Workstation; Secure Storage on Workstation Plus or OpenLab Server (OpenLab ECM XT); or OpenLab ECM. Across these backends it is verifying the same underlying promises about how data is handled.

  • Files and folders survive a full lifecycle. Folders are created, copied, moved, renamed, and deleted, and files are uploaded, downloaded, copied, and moved, with each step confirmed.
  • Stored data is intact. A downloaded file is compared by checksum against what was uploaded, so the storage system is shown to return exactly what it was given.
  • Versioning is honored. Re-uploading a file verifies that its revision increments on backends that support versioning.
  • Access is controlled. The test checks folder permissions.
  • Operations are traceable. Where activity-log checks apply, the test verifies the expected entries.

On a local file system the test concentrates on the file and folder operations and their integrity checks; on OpenLab ECM and Secure Storage it additionally covers versioning and search. Only OpenLab ECM includes check-in, checkout, electronic signing, file associations, and user-defined attributes. The test creates the folder structures and users it needs, then cleans them up when it finishes.

The test is meaningful only where there is a supported storage system to exercise. On an unsupported storage backend the test is disabled and explains why rather than running an empty check.

Why it needs a license and a privileged user​

The Storage System Test requires a license — the same license that covers the Security Test — so one license entitles a machine to run both. On Workstation Plus the license is included; on other products it is purchased and installed separately. The license check runs at the start of execution and the test fails there if no license is available.

The account that executes the test needs the privileges required by its storage backend. Secure Storage requires Manage Security, View Activity Log, and Delete content of project. OpenLab ECM requires ECM content and system permissions; Local File System requires no additional test-specific privileges beyond the base Test Services access. See Roles and privileges. If a service account is configured, these requirements apply to that account.

Relationship to the Security Test​

The Security Test and Storage System Test can run concurrently, including under domain authentication. Use separate test users for the two tests. If both tests share domain users and Remove users after tests is enabled for the Security Test, one test can delete an account that the other still needs and cause it to fail. Avoid overlapping runs with that configuration, including runs started on different machines.

Configuration​

Most configurations need no setup. Configuration is required for Secure Storage with domain authentication, where a Configure button lets you supply the two test users. For an OpenLab ECM backend, configuration is optional and controls the file-search check, including how long the test waits for an uploaded file to be indexed before searching for it. The quick-search check (Verify quick search by uploading a file and searching for it) is selected by default, and the indexing wait time defaults to 600 seconds (10 minutes) and can be set as high as 9999 seconds for an environment where indexing is slow. For the steps, see Run verification tests.

Test accounts and activity logs​

The administrator and non-administrator test accounts exercise access and permissions. Configuring a service account to execute the run does not replace these test accounts. On Secure Storage with domain authentication, you still configure both test users. With internal authentication, Test Services creates them automatically.

Where activity logging applies, entries identify the account that performs each logged action. The execution account and both test accounts can therefore appear in the activity log for the same run. For example, a test user's login is recorded under that test user's identity.

Where it fits​

The Storage System Test report records the storage product and version, the configuration, the test users and roles, each sub-test result, and the activity-log checks. It is 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.

See also​

Last updated: