Skip to content

Behavioural Test Audit Closure

Date checked: 2026-05-06

This note records closure of the manual behavioural-test audit roadmap item. It does not close the broader release target of pushing total coverage toward 100 percent.

Audit Command

The behavioural inventory command was:

./.venv-linux/bin/python tools/audit_test_behaviour.py --json

The smoke-only query was:

./.venv-linux/bin/python tools/audit_test_behaviour.py --json \
  | jq -r '.[] | select((.smoke_only_tests|length)>0 or .test_count==0)'

Result

Current inventory:

Metric Value
Test modules inventoried 319
Modules with smoke-only tests 0
Empty test modules reported by the audit 0

The audit therefore no longer reports test modules whose local tests lack a behavioural contract signal.

Production Gate Extension

As of 2026-05-18, the audit helper also emits an aggregate quality_gate object and can fail on explicit behavioural-density thresholds:

./.venv-linux/bin/python tools/audit_test_behaviour.py \
  --min-assertion-density 1.0 \
  --min-raises-contract-density 0.05 \
  --fail-on-quality-gate

The density gate is intentionally separate from line coverage. It measures whether tests carry local behavioural constraints, not whether a line was executed. Release closure can therefore require both a coverage threshold and a behavioural-quality threshold without treating superficial execution as proof.

Closure Basis

The closure follows the earlier targeted hardening passes recorded in the roadmap, including:

  • topological coupling guards;
  • readout-matrix guards;
  • public API export-count contracts;
  • backend registry no-op and state contracts;
  • phase-artifact boundary contracts;
  • VQLS denominator guard contracts;
  • STDP pipeline update contracts;
  • Rust benchmark timing contracts;
  • notebook and example workflow contracts;
  • mutation-test expansions across XY Kuramoto, backend, bridge, DLA parity, and mitigation modules;
  • mock/stub and full-suite ordering audits.

Remaining Boundary

This closure means the test suite no longer has smoke-only modules according to the committed audit tool. It does not mean:

  • every scientific path has executed hardware validation;
  • every module has mutation-score evidence;
  • total coverage has reached 100 percent;
  • QPU execution claims are validated.

The remaining release task is the separate coverage and test-quality closure item that tracks the documented ~97.6 % coverage baseline toward 100 percent.