Parallel Test Fixing

Workflow

1. Run the Full Test Suite

npm test -- --no-coverage 2>&1 || true

2. Group Failures

• Jest:

  FAIL src/components/Button.test.tsx

• Vitest:

  FAIL src/utils/format.test.ts

• Pytest:

  FAILED tests/test_api.py::test_create_user

3. Launch Parallel Subagents

generalPurpose

Task: Fix the failing tests in <file>

The test file is: <path>
The test command is: <command to run just this file>
The error output was:
<paste the relevant failure output>

Steps:
1. Read the test file and the source file it tests
2. Understand why each test is failing
3. Fix the source code (preferred) or update the test if the test is wrong
4. Run the single test file to confirm it passes
5. Report what you changed and why

4. Collect Results

• Which tests were fixed
• What files were changed
• Whether the fix might conflict with another subagent's changes

5. Verify

npm test

Tips

• If two failing tests share the same source file, assign them to the same subagent to avoid edit conflicts
• Set a timeout — if a subagent is stuck for 5+ minutes, check its progress
• For large test suites (50+ failures), batch into groups of 5-10 per subagent rather than one-per-file
• Use

  best-of-n-runner

  subagents if you want isolated worktrees for each fix attempt