Minimal Test Plan

Use to decide the smallest effective tests for a change.

Steps

1. •Identify risk areas

• •Data writes, auth, external calls, concurrency, migrations

1. •Choose minimal checks

• •Unit: logic/edge cases in changed functions
• •Integration: real deps (DB/API) on the critical path
• •Smoke: user/system flow proving the feature works end-to-end

1. •Define commands and data

• •List exact commands to run; note fixtures or env needed

1. •Run or note blockers

• •Run the fastest meaningful subset; note anything skipped and why

1. •Report

• •Tests run + results; tests skipped + rationale

Outputs

• •Short test matrix: which tests, commands, data, results/omissions

When to stop and ask

• •If change is high-risk but only trivial tests are proposed
• •If required fixtures/env are unavailable