Core terms
- Autopilot
- QTXpert’s autonomous testing layer. It runs approved coverage inside an explicit operating boundary and returns status and evidence.
- Quality loop
- The connected path from product context and understanding to coverage, governed execution, evidence, and a release decision.
- Traceability
- The connection between the requirement, the coverage created from it, the run that exercised it, and the evidence that supports the result.
- Coverage
- The set of functional and quality-attribute checks chosen to reduce uncertainty for a workflow or release.
- Evidence
- The status, artifacts, and context that let a reviewer understand what happened and why a decision followed.
- Approval gate
- A deliberate point where a person must review or authorize an action before a governed workflow continues.
- Failure policy
- The rule for how a workflow handles a failed, blocked, ambiguous, or transient result.
- Release confidence
- A reasoned view of known evidence and remaining risk, not a claim that a release is risk-free.
How to use the vocabulary
When a team says “the test passed,” ask which coverage was in scope, what evidence was captured, and what decision the result supports. Shared terms are useful when they make the next action clearer.
Make the noun explicit. Distinguish the requirement, the test case, the run, the evidence, and the decision. That small habit keeps quality discussions from collapsing into one ambiguous status.
See the terms in action
Start with the QTXpert quality loop, then use the Autopilot guide to see how autonomy and governance fit together.