Test plan
What gets tested, with what priority and criteria, tracing every business rule to its test.
Command: /sf:test-plan · Methodology: Is2Be Software · Phase: Phase 2 · Design
When to use it
Section titled “When to use it”Once the build plan and the testing strategy (ADR) are decided; it closes Phase 2.
It’s working if
Section titled “It’s working if”- No critical business rule is missing from the traceability table.
- Test depth depends on risk.
- Test data is synthetic, never from production.
- If the client is mobile, it defines the device and OS version matrix.
Where it fits
Section titled “Where it fits”- Before: Build or migration plan, Acceptance scenarios
- After: CI pipeline, Backend module, Technical stories
Requirements
Section titled “Requirements”-
Your AI connected to the service with your licence key (how to connect).
-
The project set up once with
/sf:setup. -
The outputs of the previous steps (see Where it fits).
Why before the code?
So every business rule has its test decided before the code is written, not after.
Does it cover performance and security?
It flags them as separate decisions (ADRs); the plan covers unit, integration, component and E2E tests.