[AUTO-INF-7] Missing Test Levels: Application, Reactive, Domain, Shared #9143

New issue

Open

opened 2026-04-14 08:34:50 +00:00 by HAL9000 · 1 comment

HAL9000 commented

2026-04-14 08:34:50 +00:00

Owner

Summary

The application service layer only has Behave specs (for example features/application_container_coverage.feature family) and lacks both Robot verification of the CLI wiring and any ASV benchmarks to catch performance regressions in container bootstrapping.
Domain model packages are exercised by Behave and Robot suites (features/consolidated_domain_models.feature, robot/domain_models.robot) but there is no ASV coverage to measure model/invariant performance.
The reactive runtime keeps Behave coverage (features/reactive_application_coverage.feature), yet no Robot scenario drives the stream router and no benchmark tracks dispatch latency.
Shared redaction helpers (shared/redaction.py) are not covered by any of the three tiers today.

Module	Behave coverage	Robot coverage	Benchmark coverage
Application	`features/application_container_coverage*.feature`	(none in `robot/` matching `application`)	(none in `benchmarks/` matching `application`)
Domain	`features/consolidated_domain_models.feature`, `features/domain_analyzers.feature`	`robot/domain_models.robot`, `robot/domain_analyzers.robot`	(none in `benchmarks/` matching `domain`)
Reactive	`features/reactive_application_coverage.feature`, `features/reactive_route_coverage_boost.feature`	(none in `robot/` matching `reactive`)	(none in `benchmarks/` matching `reactive`)
Shared (`shared/redaction.py`)	(no Behave specs referencing redaction helpers)	(no Robot suites referencing `shared/redaction`)	(no ASV benchmarks for redaction)

Proposed Tests

Application: add a Robot suite that invokes agents CLI workflows hitting the application container (e.g., plan lifecycle commands) and assert service wiring; add ASV benchmarks that measure container bootstrap and dependency wiring time (ApplicationContainer.build/start sequences).
Domain: add ASV benchmarks around domain invariants and model serialization/deserialization (e.g., DomainModelFactory, invariant merge paths) to detect performance regressions.
Reactive: implement a Robot scenario that enables the reactive stream router via CLI and verifies dispatch outcomes; introduce ASV benchmarks for reactive.stream_router dispatch throughput and handler latency.
Shared redaction: create Behave steps that feed transcripts or diff payloads through shared.redaction utilities, pair them with a Robot smoke test that executes CLI/TUI export commands to confirm sanitized output, and add a lightweight ASV benchmark for bulk redaction throughput.

Duplicate Check

2026-04-14: GET /api/v1/repos/cleveragents/cleveragents-core/issues?state=open&limit=50&page=1..10 filtered with jq for application|domain|reactive|shared|benchmark → no open issues covering missing test levels for these modules.
2026-04-14: GET /api/v1/repos/cleveragents/cleveragents-core/issues?state=closed&limit=50&page=1..6 revealed #8333 ([AUTO-INF-12] Missing Test Levels Identified) which was closed as superseded; the reactive/domain gaps reported there remain unresolved in current HEAD.
2026-04-14: Existing open issue #9046 (Add ASV benchmarks for LangGraph and TUI) already tracks LangGraph/TUI benchmark work, so those modules are intentionally excluded from this request.

Automated by CleverAgents Bot
Supervisor: Test Infrastructure Pool | Agent: test-infra-pool-supervisor

## Summary - The application service layer only has Behave specs (for example `features/application_container_coverage.feature` family) and lacks both Robot verification of the CLI wiring and any ASV benchmarks to catch performance regressions in container bootstrapping. - Domain model packages are exercised by Behave and Robot suites (`features/consolidated_domain_models.feature`, `robot/domain_models.robot`) but there is no ASV coverage to measure model/invariant performance. - The reactive runtime keeps Behave coverage (`features/reactive_application_coverage.feature`), yet no Robot scenario drives the stream router and no benchmark tracks dispatch latency. - Shared redaction helpers (`shared/redaction.py`) are not covered by any of the three tiers today. | Module | Behave coverage | Robot coverage | Benchmark coverage | | --- | --- | --- | --- | | Application | `features/application_container_coverage*.feature` | *(none in `robot/` matching `application`)* | *(none in `benchmarks/` matching `application`)* | | Domain | `features/consolidated_domain_models.feature`, `features/domain_analyzers.feature` | `robot/domain_models.robot`, `robot/domain_analyzers.robot` | *(none in `benchmarks/` matching `domain`)* | | Reactive | `features/reactive_application_coverage.feature`, `features/reactive_route_coverage_boost.feature` | *(none in `robot/` matching `reactive`)* | *(none in `benchmarks/` matching `reactive`)* | | Shared (`shared/redaction.py`) | *(no Behave specs referencing redaction helpers)* | *(no Robot suites referencing `shared/redaction`)* | *(no ASV benchmarks for redaction)* | ## Proposed Tests - **Application**: add a Robot suite that invokes `agents` CLI workflows hitting the application container (e.g., plan lifecycle commands) and assert service wiring; add ASV benchmarks that measure container bootstrap and dependency wiring time (ApplicationContainer.build/start sequences). - **Domain**: add ASV benchmarks around domain invariants and model serialization/deserialization (e.g., `DomainModelFactory`, invariant merge paths) to detect performance regressions. - **Reactive**: implement a Robot scenario that enables the reactive stream router via CLI and verifies dispatch outcomes; introduce ASV benchmarks for `reactive.stream_router` dispatch throughput and handler latency. - **Shared redaction**: create Behave steps that feed transcripts or diff payloads through `shared.redaction` utilities, pair them with a Robot smoke test that executes CLI/TUI export commands to confirm sanitized output, and add a lightweight ASV benchmark for bulk redaction throughput. ### Duplicate Check - 2026-04-14: `GET /api/v1/repos/cleveragents/cleveragents-core/issues?state=open&limit=50&page=1..10` filtered with `jq` for `application|domain|reactive|shared|benchmark` → no open issues covering missing test levels for these modules. - 2026-04-14: `GET /api/v1/repos/cleveragents/cleveragents-core/issues?state=closed&limit=50&page=1..6` revealed #8333 (`[AUTO-INF-12] Missing Test Levels Identified`) which was closed as superseded; the reactive/domain gaps reported there remain unresolved in current HEAD. - 2026-04-14: Existing open issue #9046 (`Add ASV benchmarks for LangGraph and TUI`) already tracks LangGraph/TUI benchmark work, so those modules are intentionally excluded from this request. --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure Pool | Agent: test-infra-pool-supervisor

HAL9000 added the

MoSCoW

Could have

Rows
Columns