Agentic framework for integration, end2end, multiuserinteraction, security testing based on usecases.
tegwick
faef069b17
Consolidation before application. Everything TD-WP-0002 demonstrated rests on one use case, one application and one token-free runtime; three of the project's own findings say that is too narrow a base for real work. - T01 bounded live-model experiment: settles F-0005 (capability) and F-0007 (economics) in one run. Needs an operator decision on cost ceiling first. - T02 two further use cases: the model was designed against Alice/Bob/Carol, so of course it fits. What it has to grow to express something else is the evidence. - T03 build the dropped-identifier mutation side to ten; H-001 currently turns on three. - T04 settle every gated concept - Temperature and energy.py are used in a decision or removed. Extending a gate is not a result. - T05 decide how claims are expressed, answerable only after T02. - T06 browser-engine driver if warranted (blocked on Playwright). - T07 measure time to express a use case - first in the scorecard, never measured, and reconstructable only during T02. - T08 readiness review with explicit criteria for real-system application. Applying test-driver to audit-core is explicitly out of scope and gated on T08. Coordination note added: another session works in this repo, so staging must be explicit and interface changes published. 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 |
||
|---|---|---|
| crystallized | ||
| docs | ||
| history | ||
| lab | ||
| research | ||
| scenarios | ||
| src/testdriver | ||
| tests | ||
| usecases | ||
| 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
usecases/ durable test intent, including not-yet-runnable use cases
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