The Tests page is the complete checklist behind your compliance program — every automated and manual check across every framework you have enabled, all in one table.
Reading the table
All / Passing / Failing / Excluded tabs filter the list.
Each row's Run Status shows the current result, and Frameworks shows which framework(s) that test counts toward.
A banner like "7 tests are not linked to any active framework" means those tests aren't contributing to any framework's readiness — safe to disable if you don't need them, via the Disable all shortcut in that banner.
Opening a test
Click into any test to see its full evidence: which specific resources were checked, why they passed or failed, remediation guidance, and which controls it feeds into.
Muting a resource
Sometimes one specific resource inside a test is a known, accepted exception — a domain that's intentionally not proxied through your WAF, for example — while the rest of that test should keep running normally. Select the resource's checkbox and use Deactivate:
This moves just that resource to the test's Deactivated tab — it stops counting toward the test's pass/fail status, but everything else the test checks keeps running as normal. This is scoped to this one test; the same resource can still show up (and still needs handling) under a different test that also happens to check it.
Re-running tests
Re-run all tests (top of the Tests page) re-triggers every test — automated tests already run daily on their own, so this is mainly useful right after a bulk fix, and can take 5–10 minutes to fully reflect.
To check a single fix, it's faster to open that one test and trigger just it, rather than re-running everything.
Automated vs. manual tests
Not every row here is a live integration check — some are manual/document tests, satisfied by uploading evidence rather than an automated scan. Both types show up in the same table and count the same way toward a control or framework's readiness; the icon next to each test's name is the quickest way to tell them apart.