Assertions should witness the promise, not only the UI state.
QA
Praxis for QA
A passing test can miss the promise people rely on.
Start in the practice language people already use. Then use Praxis to distinguish the signal from the promise, the carrier from the capability, and proof from the status label.
Diagnostic move
Translate the practice into promise work.
A UI test may confirm that a green checkmark appears after submission. The Praxis test asks whether the status is allowed to appear before proof exists, and turns false-success examples into anti-golden traces.
The question is not whether the familiar artifact exists. The question is whether that artifact witnesses the promise people actually rely on.
- Signal
- The label, state, event, journey step, or metric that says something happened.
- Promise
- What someone treats as true because the product signaled it.
- Carrier
- Where, through whom, or through what the promise was encountered.
- Proof
- Evidence that would matter to the relying person, not only the internal system.
- Repair
- The owner and path when the promise cannot hold.
Translation
How Praxis enters this practice.
False success cases become anti-golden traces.
Quality gates should block labels that outpace proof.
Signals to inspect
Start with one label.
verified
synced
completed
safe to proceed
Worksheet
Keep the review concrete.
Download the worksheet, choose one signal, and write the proof and repair path before discussing the theory.