Full-flow tests (no UI)
Walk through a critical flow end to end against real infrastructure, with no UI — the E2E equivalent for microservices, events or CLIs.
Command: /sf:e2e-tests-no-ui · Methodology: Is2Be Software · Phase: Phase 5 · Testing
When to use it
Section titled “When to use it”When a critical flow is complete and there’s no UI driving it.
It’s working if
Section titled “It’s working if”- It runs against the project’s real infrastructure, never mocks of it.
- It covers the happy path and at least one real domain failure.
- If there are async steps, it waits with a bounded timeout, never a fixed sleep.
Where it fits
Section titled “Where it fits”- Before: Integration tests
- After: CD pipeline
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).