Scope and expected behavior
- Name important user and operating tasks.
- Record roles, starting state and expected outcome.
- List known failures and relevant nearby cases.
- State what remains outside the first scope.
Planning checklist
Prepare the conditions a useful test needs.
Use these prompts for your own notes. This page does not collect answers or upload logs.
Reviewed October 16, 2026 ยท Faith Forge Labs
Environment and data
- Identify a suitable controlled environment.
- Prepare fictional fixtures and restore conditions.
- Separate test recipients, payments and external effects.
- Agree any necessary live action explicitly.
Execution and investigation
- Record the version and conditions checked.
- Keep reproduction steps and expected versus actual results.
- Distinguish passes, failures, skipped and unsupported checks.
- Retest repaired behavior and relevant adjacent paths.
Release and handoff
- Agree release and stopping conditions.
- Preserve useful reports and known limitations.
- Identify or classify approved test records.
- Name test-maintenance and support owners.
Discuss the first test scope or review the delivery process.