TEST-INFRA: [test-data-quality] Hardcoded local paths in test data fixtures #7074

Open
opened 2026-04-10 07:29:27 +00:00 by HAL9000 · 1 comment
Owner

Metadata

  • Branch: task/test-infra-hardcoded-paths-in-fixtures
  • Commit Message: test(fixtures): replace hardcoded local paths in test data fixtures with portable alternatives
  • Milestone: (none — backlog, see note below)
  • Parent Epic: #5407

Duplicate Check

  • Search queries: "hardcoded paths", "test data paths", "fixture paths"
  • Results: 0 issues found for these queries.

Description

The test data fixture at features/fixtures/m1/git_repo.json contains hardcoded local file paths for the remote_url field (e.g., file:///tmp/m1-smoke-test-repo.git).

This makes the tests less portable and can cause them to fail in environments where the /tmp directory is not accessible or shared in the same way, such as in some CI/CD container-based environments.

Subtasks

  • Identify all instances of hardcoded local paths in test data fixtures.
  • Replace hardcoded paths with a more portable solution, such as using a temporary directory library or a relative path that can be resolved at runtime.
  • Ensure that all tests that use these fixtures continue to pass after the changes.

Definition of Done

  • All hardcoded local paths in test data fixtures have been replaced with a portable solution.
  • All related tests pass successfully in both local and CI environments.
  • All nox stages pass
  • Coverage >= 97%

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

## Metadata - **Branch**: `task/test-infra-hardcoded-paths-in-fixtures` - **Commit Message**: `test(fixtures): replace hardcoded local paths in test data fixtures with portable alternatives` - **Milestone**: *(none — backlog, see note below)* - **Parent Epic**: #5407 ## Duplicate Check - Search queries: "hardcoded paths", "test data paths", "fixture paths" - Results: 0 issues found for these queries. ## Description The test data fixture at `features/fixtures/m1/git_repo.json` contains hardcoded local file paths for the `remote_url` field (e.g., `file:///tmp/m1-smoke-test-repo.git`). This makes the tests less portable and can cause them to fail in environments where the `/tmp` directory is not accessible or shared in the same way, such as in some CI/CD container-based environments. ## Subtasks - [ ] Identify all instances of hardcoded local paths in test data fixtures. - [ ] Replace hardcoded paths with a more portable solution, such as using a temporary directory library or a relative path that can be resolved at runtime. - [ ] Ensure that all tests that use these fixtures continue to pass after the changes. ## Definition of Done - All hardcoded local paths in test data fixtures have been replaced with a portable solution. - All related tests pass successfully in both local and CI environments. - All nox stages pass - Coverage >= 97% > **Backlog note:** This issue was discovered during autonomous operation > on milestone v3.2.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: new-issue-creator
Author
Owner

Verified — Test data quality: hardcoded local paths in test data fixtures. MoSCoW: Could-have. Priority: Low.


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

✅ **Verified** — Test data quality: hardcoded local paths in test data fixtures. MoSCoW: Could-have. Priority: Low. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
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#7074
No description provided.