814 B
814 B
Assertions and Test Oracles
Use this file when translating requirements into checks.
Turn Requirements into Assertions
- Convert each requirement into observable UI state (text or stability).
- Prefer
wait --assertfor pass/fail semantics. - Collect evidence with a final
screenshotbefore cleanup.
Assertion Patterns
- Text presence:
agent-tui wait "Expected" --assert - Text gone:
agent-tui wait "Expected" --gone --assert - Stability:
agent-tui wait --stable --assert
Validation Strategy
- For static UI: text snapshot +
waitis enough. - For dynamic UI: insert
wait --stablebefore each action.
Reporting
- Report: scenario, actions taken, assertions run, and final evidence (screenshot output).
- If an assertion fails, include the last screenshot and the expected condition.