4.5Test Execution Workflows

Status Transitions

Status	Meaning	Next Steps
Not Executed	Test has not been run yet	Execute the test
In Progress	Tester is currently executing	Complete and set final status
Passed	All expected results verified	No action needed
Failed	Actual result differs from expected	File a bug, link to test
Blocked	Cannot execute due to dependency	Document blocker, notify team
Skipped	Intentionally not executed this cycle	Document reason (e.g., feature not deployed)

Execution Best Practices

1. Execute in priority order: Run smoke tests and critical path tests first. If those fail, investigate before running the full suite.
2. Document failures immediately: Do not batch failure documentation for the end of the day. File the bug while the context is fresh.
3. Link failures to defects: Every failed test should have a linked bug ticket. This creates traceability.
4. Re-execute after fixes: When a bug is fixed, re-run the failed test and update its status.
5. Update blockers daily: Blocked tests should be reviewed in standup. Do not let them sit blocked for the entire sprint.