ENTITY Documentation Portal
Developer manual · ENTITY v3.4.3 · verification

Testing

ENTITY testing is designed around invariants and evidence boundaries, not only code coverage. A passing test means the tested condition passed in the documented environment; it does not automatically prove untested deployments, legal conclusions or external-world truth.

Current target: ENTITY v3.4.3. The signed release tag resolves to commit 528b70aabd05b1e930b77e4933f157731e47274f. BTDU remains component version 3.4.2 unchanged.

Current reference regression

git clone https://github.com/blackmore-technology-group/ENTITY.git
cd ENTITY
git checkout v3.4.3
python -m pip install -r requirements.txt
python -m compileall -q src sdk protocol
python -m unittest discover -s tests -v

Current release qualification

The v3.4.3 release records 76/76 PASS for the Issue #28 remediation module and 279/279 PASS for the full repository source suite, with exit code 0. Those results apply to the published v3.4.3 release scope.

Inherited evidence

Compiled Rust clean-room/conformance qualification and real-world BTDU training qualification are carried forward from v3.4.2 because the qualified components/paths were unchanged. They are inherited qualification records, not re-executed v3.4.3 test runs.

What to test

Negative testing

Invalid vectors are first-class. Tests should deliberately substitute originators, stewards, signatures, hashes, authorities, profiles, rights and provenance references and verify that the system fails closed.

Recovery tests

A meaningful destructive-recovery test captures pre-recovery roots, removes or isolates mutable state, restores from the qualified backup/export, then recomputes semantic/content roots and reverifies signatures, rights and evidence.

Environment-gated tests

Where a test requires hardware custody, multiple physical hosts, external data, a third-party implementation or wall-clock duration, record the gate explicitly instead of treating a skipped or inherited result as a fresh pass.

Historical reproduction

Use v3.4.2 only when reproducing evidence that was actually sealed against v3.4.2. Preserve its exact commands, hashes and environment labels rather than relabeling the result as a v3.4.3 execution.