Library / Systems Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 08:01:07 UTC · snapshot created 2026-10-03 08:04:31 UTC · last check 2026-10-03 08:10:10 UTC

SYSE.31:4.1 - Connect a check to the decision

Name the changed behavior, the assertion under test and the result consumer. Recover the application team’s acceptance meaning rather than deriving it from current implementation. A test that repeats the implementation’s mistaken assumption is not an independent answer to the user question.

Bind each result to the source or artifact actually exercised, relevant configuration, test input and conditions. Distinguish a test description from a completed run. A missing run, lost observation or wrong artifact cannot be reported as a pass.

Begin with a small set that discriminates the consequential failures for the current change. When necessary behavior is not specified well enough to judge, return that precise question to its owner. Do not hide it behind a large existing test count.