Gate: test-level-codes
Not in the default catalog: init does not seed it; a project declares it with check:.
| Property | Value |
|---|---|
| Checker | test-level-codes |
How it measures
Section titled “How it measures”A feature scenario is tagged with its test level (@unit-level, @vr-level, or the project’s own
names) and references rules of the spec by code. The project declares, per level, which codes it
accepts, in the levels of this gate’s own entry under gates:: a list of patterns to allow, a list to
exclude, or neither. This gate confronts every scenario with the filter of each level it is tagged
with, and names the codes the level does not accept.
It is the general form of a naming rule between level and code, and every rule of that kind is
configuration, not a gate of its own. In the reference app, 9 scenarios tagged with its visual level
had no -VR code, so the gate that asks for a baseline image never asked, and one -VR code sat
under the integration level. With the visual level allowing only -VR$ and the other levels
excluding it, both show up here.
Declaring it
Section titled “Declaring it”gates: - name: test-level-codes check: test-level-codes