TEST-INFRA: [test-data-quality] Externalize test data from helper scripts #3641

Open
opened 2026-04-05 21:02:42 +00:00 by freemo · 1 comment
Owner

Metadata

  • Branch: refactor/test-data-quality/externalize-robot-test-data
  • Commit Message: refactor(test-infra): externalize test data from robot helper scripts into JSON/YAML files
  • Milestone: (backlog — see note below)
  • Parent Epic: #2810

Summary

Our Robot Framework tests rely heavily on external Python helper scripts to generate and manage test data. This makes it difficult to see the test data at a glance and to modify it without changing the test logic. We should externalize the test data from these scripts into a more accessible format, such as JSON or YAML files.

Background

Externalizing test data is a best practice that helps to separate the test data from the test logic. This makes the tests more maintainable, reusable, and easier to understand.

Subtasks

  • Identify all Python helper scripts in the robot/ directory that are used to generate or manage test data
  • For each identified script, extract the hardcoded test data into a separate JSON or YAML file alongside the script
  • Update each helper script to read test data from the corresponding external file instead of embedding it inline
  • Update any Robot Framework .robot test files that reference these helpers to ensure they still work correctly with the new data-driven approach
  • Verify all Robot Framework integration tests still pass after the refactoring (nox -e integration_tests)

Definition of Done

  • All hardcoded test data has been externalized from Python helper scripts in the robot/ directory into JSON or YAML files
  • Each helper script reads its test data from the corresponding external file
  • No test logic has been changed — only data has been moved
  • All Robot Framework integration tests pass after the refactoring
  • All nox stages pass
  • Coverage >= 97%

Backlog note: This issue was discovered during autonomous operation
on milestone v3.7.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: Test Infrastructure | Agent: ca-new-issue-creator

## Metadata - **Branch**: `refactor/test-data-quality/externalize-robot-test-data` - **Commit Message**: `refactor(test-infra): externalize test data from robot helper scripts into JSON/YAML files` - **Milestone**: *(backlog — see note below)* - **Parent Epic**: #2810 ## Summary Our Robot Framework tests rely heavily on external Python helper scripts to generate and manage test data. This makes it difficult to see the test data at a glance and to modify it without changing the test logic. We should externalize the test data from these scripts into a more accessible format, such as JSON or YAML files. ## Background Externalizing test data is a best practice that helps to separate the test data from the test logic. This makes the tests more maintainable, reusable, and easier to understand. ## Subtasks - [ ] Identify all Python helper scripts in the `robot/` directory that are used to generate or manage test data - [ ] For each identified script, extract the hardcoded test data into a separate JSON or YAML file alongside the script - [ ] Update each helper script to read test data from the corresponding external file instead of embedding it inline - [ ] Update any Robot Framework `.robot` test files that reference these helpers to ensure they still work correctly with the new data-driven approach - [ ] Verify all Robot Framework integration tests still pass after the refactoring (`nox -e integration_tests`) ## Definition of Done - [ ] All hardcoded test data has been externalized from Python helper scripts in the `robot/` directory into JSON or YAML files - [ ] Each helper script reads its test data from the corresponding external file - [ ] No test logic has been changed — only data has been moved - [ ] All Robot Framework integration tests pass after the refactoring - [ ] All nox stages pass - [ ] Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.7.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: Test Infrastructure | Agent: ca-new-issue-creator
Author
Owner

Issue triaged by project owner:

  • State: Verified
  • Priority: Backlog — Test infrastructure refactoring. No behavior change; improves test maintainability.
  • Story Points: 5 — L — Requires identifying all helper scripts, extracting data, updating scripts to read from files, and verifying all tests still pass.
  • MoSCoW: Could Have — This is a refactoring task (no behavior change) that improves test data management. Desirable but not necessary for any milestone.
  • Parent Epic: #2810

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

Issue triaged by project owner: - **State**: Verified - **Priority**: Backlog — Test infrastructure refactoring. No behavior change; improves test maintainability. - **Story Points**: 5 — L — Requires identifying all helper scripts, extracting data, updating scripts to read from files, and verifying all tests still pass. - **MoSCoW**: Could Have — This is a refactoring task (no behavior change) that improves test data management. Desirable but not necessary for any milestone. - **Parent Epic**: #2810 --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: ca-project-owner
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#3641
No description provided.