TEST-INFRA: [test-data-quality] Improve realism of large_project_context.json #4406

Open
opened 2026-04-08 12:16:36 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Branch: test/improve-large-project-context-fixture
  • Commit Message: test(fixtures): improve realism of large_project_context.json with expanded file_entries and realistic hashes
  • Milestone: (backlog — see note below)
  • Parent Epic: #396

Backlog note: This issue was discovered during autonomous operation
on milestone v3.4.0. It does not block milestone completion and has been
placed in the backlog for human review and future milestone assignment.

Background

The test data in features/fixtures/m5/large_project_context.json is used to simulate a large project scenario for ACMS context pipeline tests. Currently, the fixture has a mismatch between its declared file_count (500) and the actual number of entries in file_entries (5), and uses unrealistic placeholder hashes. This reduces the fidelity of tests that rely on this fixture to validate large-project behaviour.

Current State

  • The file_count is set to 500, but the file_entries array only contains 5 entries.
  • The file hashes in file_entries are simplistic (e.g., aabbccdd00) and not representative of real SHA-256 file hashes.

Subtasks

  • Expand file_entries in features/fixtures/m5/large_project_context.json to contain 50–100 representative entries (closer to the declared file_count of 500)
  • Replace simplistic placeholder hashes with realistic SHA-256-style hashes (64 hex characters)
  • Ensure file_count value is consistent with the number of entries (or update it to reflect the intended simulated count with a comment)
  • Verify all existing Behave scenarios that use this fixture still pass after the change
  • Run nox -e unit_tests and nox -e coverage_report to confirm no regressions

Definition of Done

  • features/fixtures/m5/large_project_context.json contains 50–100 file_entries with realistic SHA-256-style hashes
  • file_count is consistent with the fixture's intent (either matches entry count or is documented as a simulated total)
  • All Behave scenarios using this fixture pass without modification
  • All nox stages pass
  • Coverage >= 97%

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

## Metadata - **Branch**: `test/improve-large-project-context-fixture` - **Commit Message**: `test(fixtures): improve realism of large_project_context.json with expanded file_entries and realistic hashes` - **Milestone**: (backlog — see note below) - **Parent Epic**: #396 > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.4.0. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. ## Background The test data in `features/fixtures/m5/large_project_context.json` is used to simulate a large project scenario for ACMS context pipeline tests. Currently, the fixture has a mismatch between its declared `file_count` (500) and the actual number of entries in `file_entries` (5), and uses unrealistic placeholder hashes. This reduces the fidelity of tests that rely on this fixture to validate large-project behaviour. ### Current State - The `file_count` is set to 500, but the `file_entries` array only contains 5 entries. - The file hashes in `file_entries` are simplistic (e.g., `aabbccdd00`) and not representative of real SHA-256 file hashes. ## Subtasks - [ ] Expand `file_entries` in `features/fixtures/m5/large_project_context.json` to contain 50–100 representative entries (closer to the declared `file_count` of 500) - [ ] Replace simplistic placeholder hashes with realistic SHA-256-style hashes (64 hex characters) - [ ] Ensure `file_count` value is consistent with the number of entries (or update it to reflect the intended simulated count with a comment) - [ ] Verify all existing Behave scenarios that use this fixture still pass after the change - [ ] Run `nox -e unit_tests` and `nox -e coverage_report` to confirm no regressions ## Definition of Done - [ ] `features/fixtures/m5/large_project_context.json` contains 50–100 `file_entries` with realistic SHA-256-style hashes - [ ] `file_count` is consistent with the fixture's intent (either matches entry count or is documented as a simulated total) - [ ] All Behave scenarios using this fixture pass without modification - [ ] All nox stages pass - [ ] Coverage >= 97% --- **Automated by CleverAgents Bot** Supervisor: Test Infrastructure | Agent: new-issue-creator
Author
Owner

Issue triaged by project owner:

  • State: Verified — Valid test data quality improvement
  • Priority: Backlog (already set) — Does not block any milestone
  • MoSCoW: Could Have — Improves test realism but not essential
  • Story Points: 2 — S — Fixture data update
  • Assignee: HAL9000

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

Issue triaged by project owner: - **State**: Verified ✅ — Valid test data quality improvement - **Priority**: Backlog ✅ (already set) — Does not block any milestone - **MoSCoW**: Could Have — Improves test realism but not essential - **Story Points**: 2 — S — Fixture data update - **Assignee**: HAL9000 --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner
HAL9000 self-assigned this 2026-04-08 12:24:18 +00:00
HAL9000 added this to the v3.5.0 milestone 2026-04-08 17:42:54 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#396 Epic: ACMS Context Pipeline
cleveragents/cleveragents-core
Reference
cleveragents/cleveragents-core#4406
No description provided.