Manifestly: A Checklist App for Teams

Verify the title names the scenario, not the screen

Confirm the test ID follows the suite naming convention

Link the test case to its Jira ticket or user story

Validate stated preconditions and environment requirements

Classify the test data source

Confirm PII has been scrubbed from production-clone fixtures

Document upstream and downstream test dependencies

Walk through each step for clarity and ordering

Verify expected results are stated for every step

Check that assertions use specific matchers

Cover at least one negative or edge-case path

Review the post-execution system state description

Confirm cleanup reverts database and filesystem changes

Verify external resources are released after teardown

Map the test case back to its acceptance criteria

Determine whether the test exercises a regulated data path

Cross-reference the regulatory control evidenced by the test

Run a spelling and grammar pass on the case description

Commit the test case to the version-controlled suite

Record the peer reviewer's decision

File a rework ticket for the rejected test case

Free Checklist Templates for Test Automation