tests/ mirrors behavior, not marketing. Subfolders should reveal the domain
under test. Benchmark-specific checks live in tests/benchmarks/.
benchmarks/: regression-gate and benchmark-runner tests.calibration/: calibration workflow, gate, intake, and policy-version tests.external/: external prediction workflow tests.lab/: lab handoff, data-return validation, and pass/fail tests.novelty/: novelty scoring and novelty-pressure tests.release/: release artifact and reproducibility tests.waves/: wave-program gate and panel-contract tests.- remaining top-level tests: package, CLI, scoring, selection, calibration, and evidence coverage awaiting further taxonomy work.
- Flowchart
flowchart TD
Change["Code or docs change"] --> TestSel["Select relevant tests"]
TestSel --> Bench["tests/benchmarks"]
TestSel --> Domain["other domain tests"]
Bench --> Verdict["pass/fail evidence"]
Domain --> Verdict
- Component Diagram
flowchart LR
Tests --> BenchmarkTests["tests/benchmarks"]
Tests --> DomainTests["other test modules"]
BenchmarkTests --> BenchScripts["scripts/benchmarks"]
DomainTests --> Src["src/openamp_foundry"]
- Sequence Diagram
sequenceDiagram
participant Dev
participant Pytest
participant Test as Test module
participant Code as Repo code
Dev->>Pytest: run targeted suite
Pytest->>Test: collect tests
Test->>Code: execute behavior
Code-->>Test: result
Test-->>Dev: failure or proof