fix: Jest XML path resolution and runner support for monorepos

[mohammedahmed18]

Summary

This PR fixes two critical issues preventing CodeFlash from working in monorepo environments like Budibase when running from the workspace root.

Changes

1. Jest XML test path resolution - Handle relative paths with .. components in monorepos
2. Jest runner monorepo resolution - Find jest-runner in parent node_modules directories
3. Flexible test parsing - Allow result parsing even when test files are cleaned up

---

Problem 1: Test Path Resolution

When running CodeFlash from a monorepo root (e.g., ~/budibase), Jest XML reports contain relative paths like:

../../tests/test_validEmail__unit_test_1.test.ts

These paths couldn't be resolved because:

• The base_dir is /home/user/budibase/tests
• The path ../../tests/... needs proper resolution to find the actual file
• Test files may be cleaned up before parsing completes

Example Failure

WARNING: Could not resolve test file for Jest test: ../../tests/test_validEmail__unit_test_1.test.ts
INFO: No Jest test results parsed from jest_results.xml (found 2 suites, 60 testcases)
WARNING: Couldn't run any tests for original function validEmail

---

Problem 2: Jest Runner Resolution

When running in a monorepo package (e.g., packages/backend-core), jest-runner is installed at the workspace root:

budibase/
├── node_modules/
│   └── jest-runner/          # Installed here
└── packages/
    └── backend-core/
        └── node_modules/     # Not here

The loop-runner would fail with:

Error: codeflash/loop-runner requires jest-runner to be installed.
Please install it: npm install --save-dev jest-runner

---

Solution

1. Improved Path Resolution

# Before: Simple concatenation failed with .. paths
potential_path = base_dir / test_class_path

# After: Use .resolve() to handle .. and . components
potential_path = (base_dir / test_class_path).resolve()

2. Monorepo-Aware Jest Runner Resolution

function resolveJestRunner() {
    // Try standard resolution first (simple projects)
    try {
        return require.resolve('jest-runner');
    } catch (e) {
        // Walk up directory tree for monorepos
    }

    const monorepoMarkers = ['yarn.lock', 'pnpm-workspace.yaml', 'lerna.json'];
    let currentDir = process.cwd();

    while (currentDir !== path.dirname(currentDir)) {
        // Check for jest-runner in node_modules at this level
        const jestRunnerPath = path.join(currentDir, 'node_modules', 'jest-runner');
        if (fs.existsSync(jestRunnerPath)) {
            return jestRunnerPath;
        }

        // Stop at workspace root markers
        if (monorepoMarkers.some(marker => 
            fs.existsSync(path.join(currentDir, marker))
        )) {
            break;
        }

        currentDir = path.dirname(currentDir);
    }
}

3. Flexible Test Type Inference

# Infer test type from filename pattern when files don't exist
filename = test_file_path.name
if "__perf_test_" in filename:
    test_type = TestType.GENERATED_PERFORMANCE
elif "__unit_test_" in filename:
    test_type = TestType.GENERATED_REGRESSION

---

Testing

Before (Failure)

cd ~/budibase
codeflash --file packages/backend-core/src/utils/stringUtils.ts --function validEmail

# Output:
# WARNING: Could not resolve test file for Jest test
# ERROR: No Jest test results parsed
# ERROR: Failed to establish a baseline

After (Success)

cd ~/budibase
codeflash --file packages/backend-core/src/utils/stringUtils.ts --function validEmail

# Output:
# ✓ Generated Regression Tests - Passed: 59, Failed: 0
# ✓ Running performance benchmarks...
# ✓ Baseline established

Test Results on Budibase Monorepo

Function	Location	Behavioral Tests	Status
validEmail	packages/backend-core/src/utils/stringUtils.ts	59 passed	✅
punctuateList	packages/shared-core/src/helpers/lists.ts	51 passed	✅
isDevWorkspaceID	packages/backend-core/src/docIds/conversions.ts	63 passed	✅

---

Impact

✅ Fixes

• Jest test path resolution in monorepos
• Jest runner detection in workspaces
• Test result parsing after cleanup

✅ Maintains Backward Compatibility

• Standard require.resolve() tried first for simple projects
• Falls back to monorepo resolution only when needed
• No changes to existing non-monorepo workflows

✅ Tested On

• Budibase monorepo (Yarn workspaces)
• Running from workspace root directory
• Multiple packages: backend-core, server, shared-core

---

Files Changed

• codeflash/verification/parse_test_output.py - Path resolution with .resolve() and flexible test type inference
• packages/codeflash/runtime/loop-runner.js - Monorepo-aware jest-runner resolution

---

🤖 Generated with Claude Code

[Saga4]

Can use _find_js_project_root or _find_project_root function too to figure out the project root.

[Saga4]

We can add unit tests for figuring out root path.