TEST-INFRA: [missing-test-levels] Add ASV tests for core module #1816

New issue

Open

opened 2026-04-02 23:55:18 +00:00 by freemo · 2 comments

freemo commented

2026-04-02 23:55:18 +00:00

Owner

Metadata

Branch: test/missing-test-levels-core-asv
Commit Message: test(core): add ASV performance benchmarks for core module
Milestone: v3.8.0
Parent Epic: #933

Background and Context

The core module in src/cleveragents/core is missing ASV performance benchmarks as mandated by CONTRIBUTING.md's Multi-Level Testing Mandate:

ASV performance benchmarks (in benchmarks/) — performance regression tracking

This violates the testing standards outlined in CONTRIBUTING.md, which states: "Every coding task must include or update tests at multiple levels: unit tests, integration tests, and performance benchmarks. Testing is non-optional and is part of the definition of done for any task."

Expected Behavior

The core module has complete ASV benchmark coverage tracking performance of key operations.

Subtasks

Identify all public-facing functions and classes in src/cleveragents/core that are candidates for performance benchmarking
Create ASV benchmark suite(s) in benchmarks/ covering key core module operations
Ensure benchmarks are runnable via nox (the project's task runner)
Integrate the new benchmarks into the CI pipeline's benchmark-publish job

Definition of Done

ASV performance benchmarks exist in benchmarks/ for key core module operations
All new benchmarks run successfully via the project's nox task runner
The new benchmarks are integrated into the CI pipeline
All nox stages pass
Coverage >= 97%

Automated by CleverAgents Bot
Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

## Metadata - **Branch**: `test/missing-test-levels-core-asv` - **Commit Message**: `test(core): add ASV performance benchmarks for core module` - **Milestone**: v3.8.0 - **Parent Epic**: #933 ## Background and Context The `core` module in `src/cleveragents/core` is missing ASV performance benchmarks as mandated by CONTRIBUTING.md's Multi-Level Testing Mandate: - **ASV** performance benchmarks (in `benchmarks/`) — performance regression tracking This violates the testing standards outlined in CONTRIBUTING.md, which states: *"Every coding task must include or update tests at multiple levels: unit tests, integration tests, and performance benchmarks. Testing is non-optional and is part of the definition of done for any task."* ## Expected Behavior The `core` module has complete ASV benchmark coverage tracking performance of key operations. ## Subtasks - [ ] Identify all public-facing functions and classes in `src/cleveragents/core` that are candidates for performance benchmarking - [ ] Create ASV benchmark suite(s) in `benchmarks/` covering key `core` module operations - [ ] Ensure benchmarks are runnable via `nox` (the project's task runner) - [ ] Integrate the new benchmarks into the CI pipeline's benchmark-publish job ## Definition of Done - [ ] ASV performance benchmarks exist in `benchmarks/` for key `core` module operations - [ ] All new benchmarks run successfully via the project's nox task runner - [ ] The new benchmarks are integrated into the CI pipeline - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: ca-new-issue-creator

freemo added this to the v3.8.0 milestone

2026-04-02 23:55:31 +00:00

freemo commented

2026-04-02 23:57:30 +00:00

Author

Owner

Issue triaged by project owner:

State: Verified
MoSCoW: MoSCoW/Could Have — CI/test infrastructure improvement.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: ca-project-owner

Issue triaged by project owner: - **State**: Verified - **MoSCoW**: MoSCoW/Could Have — CI/test infrastructure improvement. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner

freemo added the

MoSCoW

Could have

label

2026-04-02 23:57:30 +00:00

freemo added a new dependency

2026-04-02 23:59:31 +00:00

#933 Epic: A2A Protocol Compliance — JSON-RPC 2.0 Framing, Standard Operations, and Extension Methods

freemo commented

2026-04-03 00:27:14 +00:00

Author

Owner