Agentic framework for integration, end2end, multiuserinteraction, security testing based on usecases.
False Adaptation Rate = 0/7 across the labelled catalogue and the three E-003 attacks. 11 of 12 mechanical mutations absorbed without a human, so the safety result is not bought by escalating everything. - classification.py: total function over three signals, rule order chosen so every rule that could excuse a regression sits after the rule that reports one. SAFE_TO_ACCEPT is a two-element closed set, asserted. - CompositeDriver plus scenarios/full_journey.py: one asset crossing both surfaces, so UI mutations are visible as surface differences while the claims they do not touch stay green. - E-003: surface substitution (new M23), concurrent mechanical+defect, evidence starvation, provenance laundering. All held. F-0006 (CONCEPT_DRIFT, resolved): the T02 design listed SEMANTIC_CHANGE as an outcome the table could produce. It cannot - M12 and M19 are behaviourally identical, as the lab has asserted since T05. PRODUCT_DEFECT and SEMANTIC_CHANGE collapse into one escalating outcome, BEHAVIOUR_CHANGED, and the distinction becomes a human adjudication. INTENT_CHANGED survives but is detected by the claim fingerprint moving, not inferred from behaviour. Two classifier defects found and fixed rather than reported: claims downstream of a failed realization now yield INCONCLUSIVE rather than FAIL (a false accusation is the mirror image of a false adaptation), and the browser driver records a page signature so surface change is detectable when the interaction path is unchanged. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 1629012@bnt-lap001 Assistant-Session: 78d4fb13-8a1e-474b-87a3-9b9261c49a39 |
||
|---|---|---|
| docs | ||
| history | ||
| lab | ||
| research | ||
| scenarios | ||
| src/testdriver | ||
| tests | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| .repo-classification.yaml | ||
| AGENTS.md | ||
| INTENT.md | ||
| pyproject.toml | ||
| README.md | ||
| SCOPE.md | ||
| WORK-RECORDS.md | ||
test-driver
Agentic framework for integration, end-to-end, multi-user interaction and security testing, driven by use cases.
Tests mature alongside the software they protect: fluid and agentic while
behaviour is changing, deterministic once it settles. See INTENT.md for the
thesis and SCOPE.md for boundaries.
Status: research prototype. The deterministic kernel runs; agentic
realization, adaptation classification and crystallization are not built yet.
Current work: workplans/TD-WP-0002-vertical-spike-crystallization.md.
Run
python3 -m pytest -q # the whole suite
python3 -m pytest -q tests/test_reference_scenario.py
No third-party dependencies. Python ≥ 3.11, pytest for the suite.
Layout
src/testdriver/ the kernel — intent, world, actions, drivers,
observers, oracles, evidence, runner
lab/ the system under test
scenarios/ reference scenarios
research/ hypotheses, experiments, findings, fitness map
docs/ concept model, improvement loop, milestones, design notes
history/ assessments and completed-work write-ups
Reading order
INTENT.md— the thesisdocs/TestDriverConceptModel.md— canonical concept setdocs/TestDriverClassificationDesign.md— why adaptation cannot normalize a defect, and where model judgment is and is not permitteddocs/TestDriverInitialMilestones.md— canonical milestones M0–M10