test(features): improve test data quality in plan persistence BDD scenarios #3581

Open
opened 2026-04-05 20:04:25 +00:00 by freemo · 0 comments
Owner

Metadata

  • Branch: test/plan-persistence/improve-test-data-quality
  • Commit Message: test(features): improve test data quality in plan persistence BDD scenarios
  • Milestone: (none — backlog)
  • Parent Epic: #3374

Background

Plan persistence BDD scenarios in features/ currently use minimal or synthetic test data that does not reflect realistic plan structures as described in the specification. This reduces the diagnostic value of failing tests and makes it harder to catch edge cases in serialisation, round-trip fidelity, and field-level validation.

Improvements include: richer fixture plans with realistic titles, descriptions, goals, and metadata; boundary-value inputs (empty strings, max-length strings, special characters); and explicit assertions on every persisted field rather than only the primary key.

Subtasks

  • Audit all existing plan persistence step definitions and identify fields that are asserted vs. silently ignored
  • Extend features/mocks/ fixtures with realistic, spec-compliant plan data (titles, descriptions, goals, tags, metadata)
  • Add boundary-value scenarios: empty optional fields, maximum-length strings, Unicode/special-character values
  • Add explicit field-level assertions for every column persisted by the plan repository
  • Ensure all new scenarios are tagged and discoverable via nox -e unit_tests
  • Verify coverage remains ≥ 97% after additions (nox -e coverage_report)

Definition of Done

  • All existing plan persistence scenarios continue to pass
  • New boundary-value and field-completeness scenarios are added and passing
  • Every persisted plan field has at least one explicit assertion in the BDD suite
  • Mock fixtures in features/mocks/ are updated to reflect realistic spec-compliant data
  • All nox stages pass
  • Coverage >= 97%

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


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

## Metadata - **Branch**: `test/plan-persistence/improve-test-data-quality` - **Commit Message**: `test(features): improve test data quality in plan persistence BDD scenarios` - **Milestone**: *(none — backlog)* - **Parent Epic**: #3374 ## Background Plan persistence BDD scenarios in `features/` currently use minimal or synthetic test data that does not reflect realistic plan structures as described in the specification. This reduces the diagnostic value of failing tests and makes it harder to catch edge cases in serialisation, round-trip fidelity, and field-level validation. Improvements include: richer fixture plans with realistic titles, descriptions, goals, and metadata; boundary-value inputs (empty strings, max-length strings, special characters); and explicit assertions on every persisted field rather than only the primary key. ## Subtasks - [ ] Audit all existing plan persistence step definitions and identify fields that are asserted vs. silently ignored - [ ] Extend `features/mocks/` fixtures with realistic, spec-compliant plan data (titles, descriptions, goals, tags, metadata) - [ ] Add boundary-value scenarios: empty optional fields, maximum-length strings, Unicode/special-character values - [ ] Add explicit field-level assertions for every column persisted by the plan repository - [ ] Ensure all new scenarios are tagged and discoverable via `nox -e unit_tests` - [ ] Verify coverage remains ≥ 97% after additions (`nox -e coverage_report`) ## Definition of Done - [ ] All existing plan persistence scenarios continue to pass - [ ] New boundary-value and field-completeness scenarios are added and passing - [ ] Every persisted plan field has at least one explicit assertion in the BDD suite - [ ] Mock fixtures in `features/mocks/` are updated to reflect realistic spec-compliant data - [ ] All nox stages pass - [ ] Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.6.0. It does not block milestone completion and has been > placed in the backlog for human review and future milestone assignment. --- **Automated by CleverAgents Bot** Supervisor: Unknown | Agent: ca-new-issue-creator
freemo added this to the v3.7.0 milestone 2026-04-05 20:16:29 +00:00
freemo removed this from the v3.7.0 milestone 2026-04-06 23:38:07 +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.

Reference
cleveragents/cleveragents-core#3581
No description provided.