Minimal Test Gate

Default Test Selection

Pick only the highest-signal cases:

1. happy path
2. one key validation or failure path
3. one archetype-specific check if it proves real value

Examples:

• gateway/proxy: valid route, invalid request, upstream failure normalization
• tool agent: tool selection, invalid tool args
• retrieval: retrieval hit, empty or no-match response
• workflow: successful step sequence, early failure reporting

Test Workflow

1. Write down the user journey or system journey you must prove.
2. Prefer the smallest failing test that demonstrates the missing behavior.
3. Implement or adjust only enough code to pass that test.
4. Rerun the smallest meaningful check after each fix.
5. Stop once the main loop is credibly proven.

Reporting Format

• Tests selected:
• Why these tests matter:
• What remains intentionally untested:

Test Standard

• make tests small
• assert stable behavior, not implementation trivia
• stop once the main loop is credibly proven

What Not To Do

• do not chase coverage numbers
• do not build a full browser suite unless the prompt depends on UI behavior
• do not add tests that duplicate the contract without adding confidence
• do not spend the final 20 minutes converting a working MVP into a full pyramid