Test cases¶
Test cases belong to the Test Protocol. Each one is linked to the requirements it verifies.
Kinds of test¶
| Kind | What it is |
|---|---|
| Automated | A pytest test, identified by its pytest node ID. |
| Scripted manual | Steps, one per line, written as action => expected result. |
| Unscripted | Exploratory testing against a session charter (in Objective). Enough on its own only for Tier 3 requirements. |
See Required assurance for which kinds each tier accepts.
Creating tests from a pytest-gxp report¶
Run pytest --gxp --gxp-output-formats=json during development and import the report with Create test cases: one automated test case is created per test, linked to the requirements in its markers. You can also add tests found by a repository scan.
Environments¶
A test case can list the environments it must pass in (for example Test and Prod). The RTM then shows the latest result in each one. See Automated runs.
Approval¶
The Test Protocol must be approved before any test can be executed for the record. After approval, test cases are locked. A test changed after it was executed is the RTM gap test-changed-since-execution.