Gate Evaluator
A gate is a set of conditions that must hold before an action may proceed. The gate evaluator judges those conditions and reports the result; it does not enforce it. Its requirements fix which findings block and which merely inform, what a blocked report must contain for anyone to act on it, and one condition that would otherwise pass in silence — a scope with nothing in it to seal.
A skipped outcome is the runner’s statement that the test did not run under one configuration. It is not a verdict on the implementation. The graph records the skip so that it mirrors the run faithfully. The gate judges the skip as absence of evidence and reports it.
Waivers
The gate evaluator shall let a valid waiver, and only a valid waiver, excuse a failing outcome, that is, an outcome whose result is failed or error. |
Software Requirement: A waiver is valid only when unexpired and its approver is authorised SEG-SREQ-059
|
The gate evaluator shall treat an excusing waiver as valid only when it has not expired and its recorded approver is authorised to grant it. |
If a failing outcome is not excused by a valid waiver, then the gate evaluator shall report that outcome as blocking. |
If a failing outcome is excused by a valid waiver, then the gate evaluator shall report that outcome as informational. |
Staleness
The gate decides staleness from the revision it is given.
The gate evaluator shall set aside, in a way its report shows, every outcome recorded against a revision other than the current one it is given. |
The gate evaluator shall treat an outcome whose recorded revision differs from the current revision it is given as absent when it judges the specification that outcome confirms. |
The gate evaluator shall report an outcome whose recorded revision differs from the current revision it is given as an informational finding in its report. |
The report and its vocabulary
Software Requirement: Every finding says where it lies, what it is, and whether it blocks SEG-SREQ-131
|
The gate evaluator shall report every finding as a diagnostic that says where the finding lies, under which named condition, and whether it blocks. |
The gate evaluator shall treat a condition reported as an error or a warning as blocking, and a condition reported as information as not blocking. |
The gate evaluator shall list in its report every strong edge in scope that is not active. |
The gate evaluator shall report a coverage gap at the requirement that lacks coverage, never at a requirement that it refines. |
If a scope’s design set is empty, then the gate evaluator shall report that scope as blocked. |
The gate evaluator shall report the condition of every diagnostic as one member of a fixed set of named conditions. |
The gate evaluator shall keep every diagnostic’s condition free of detail that varies by occurrence, such as which state an edge is in. |
The gate evaluator shall report each outcome whose result is skipped as an informational finding in its report. |
The gate evaluator shall report each outcome that the satisfaction evaluator discards as incomplete evidence as an informational finding in its report. |