diff --git a/docs/decisions/records/testing/scripted-engine-in-process-net.md b/docs/decisions/records/testing/scripted-engine-in-process-net.md index e55e68db1..ee9b61bc5 100644 --- a/docs/decisions/records/testing/scripted-engine-in-process-net.md +++ b/docs/decisions/records/testing/scripted-engine-in-process-net.md @@ -57,7 +57,8 @@ admits a sentence asserting that a specific mutation reddens — or does not red a `CLAIMS` entry in `scripts/tests/mutation_manifest.py`, executed every run; otherwise it is not written. That harness resolves a proof to `scripts/tests/` and runs pytest, so an NUnit proof cannot be declared in it and this coverage is entirely NUnit. The binder and `trim` mutants run while -building these tests therefore stay in the commit messages that ran them, dated. Durable prose carries +building these tests therefore stay in ersatztv#563 — its pull request and the commit messages that +ran them — dated. Durable prose carries the mechanism each test is built on instead — which serializer difference, which engine branch — because that is re-checkable by reading the code rather than by trusting a remembered outcome. diff --git a/docs/testing.md b/docs/testing.md index c6cd1b188..09ebf0827 100644 --- a/docs/testing.md +++ b/docs/testing.md @@ -104,7 +104,7 @@ built to separate one of them: Both are statements about the serializer and stop there — what MVC validation does with such a body belongs to the wrapper named above. What each test does to a suite when the binder is actually swapped -was measured while building it and is recorded in the commit that did so, not here: under +was measured while building it and is recorded in ersatztv#563, not here: under `testing.mutation-claims-are-executed` such a sentence is a `CLAIMS` entry in `scripts/tests/mutation_manifest.py` that executes every run or it is not written, and that harness runs pytest, so an NUnit proof cannot be declared in it.