| Term | Meaning |
|---|---|
| Test Plan | A container for a testing effort. |
| Test Suite | A folder of test cases in a plan — static, requirement-based or query-based. |
| Test Case | The work item describing what to test. |
| Test Point | A test case as it appears in one suite, for one configuration; results attach here. |
| Result / Outcome | Passed, Failed, Blocked, Not Applicable, Not Executed or None. |
| Latest result | The most recent outcome for a point — what TestPulse reports. |
| Coverage | Whether a requirement has at least one linked test. |
| Depth | Whether those tests actually cover the acceptance criteria. |
| Execution verdict | Passed / Not OK / Not Run / Not covered — a reduction of outcomes. |
| Quality Gate | The A–E grade plus GO / NO-GO verdict. |
| Traceability | The Epic → User Story → Test Case → Bug chain. |
| Tested By | The Azure DevOps link between a requirement and its test cases. |
| Extension Data | Azure DevOps storage where TestPulse keeps reports and preferences. |
Related
The Test Plans model
The core entities.
Statuses & results
Outcomes in detail.