Skip to main content

Complete a compliance test

Tests prove that a control works. Automated tests are run by your integrations; manual tests need evidence from your team. A control passes once all its tests are completed.

Where: Dashboard → Compliance → Tests, or open Tests. Click a test to open it.

See how to fix a test​

Click How to fix: on the test's row in Tests, on an integration's test list (View tests in Integrations), or next to the test's title on its page. A side panel opens with what the test checks, the steps to fix it, the evidence auditors expect and common pitfalls. Use Copy to paste it elsewhere, or Open test to go to the test from the list.

  • For manual and integration tests, the guidance is written by AI the first time anyone opens it, so it can take up to a minute. For integration tests it explains the setting to change in that tool; the next scan re-checks it. AI guidance is marked AI-generated draft; review it before acting on it.
  • Guidance written by the Vamu team is marked Written by the Vamu team.
  • Custom tests and tests linked to a policy or document have no How to fix. Complete a linked test through its policy or document.
  • If the panel says guidance isn't ready yet, click Try again after a moment.

Complete a manual test​

  1. Open the test from Tests (filter by Status, Frameworks or owner to find it).
  2. Write the Evidence description and add an Evidence attachment if you have a file.
  3. Click Update to save. The test moves to PENDING REVIEW.
  4. After checking the evidence, click Mark as completed. The test becomes COMPLETED.

Tests linked to a policy or document are completed through that policy's own workflow instead. See Write, review and publish a policy.

Work with an automated test​

  • The Resources tab shows each resource the integration checked, with Passed or Failed results.
  • Click Scan on an integration to re-check its resources for this test, or Sync to rerun the test across all of its integrations.
  • To exclude one resource from the result, use Disable Resource on it and give a reason.

To connect the tool behind a test, see Connect an integration.

Assign an owner​

Set the Owner and Departments on the test. When departments are selected, the owner must belong to at least one of them (admins can always be owners).

Mark a test out of scope​

Click Mark Out of Scope, give a Reason and a Duration (or Indefinitely). Use Reactivate to bring it back. Out-of-scope tests are listed in the Out of Scope tab.

Create a custom test​

On the Tests page, click Create Custom Test, choose the Frameworks and Controls it covers, then fill in the title, description, status, owner and evidence.

Other tabs on a test​

Evidence, Notes, History (every change made to the test) and Related Controls.