fix: use POSIX paths in jest-reporter XML test to fix Windows path escaping

On Windows, Path objects stringify with backslashes which are treated as escape
sequences in JS string literals, breaking the Node.js test script.

Co-authored-by: Aseem Saxena <aseembits93@users.noreply.github.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: 3 people

tests/test_languages/test_javascript_test_runner.py

@@ -907,15 +907,18 @@ def test_reporter_produces_valid_junit_xml(self):
 
             # Create a Node.js script that exercises the reporter with mock data
             test_script = Path(tmpdir) / "test_reporter.js"
+            # Use POSIX-style paths in JS strings to avoid backslash escape issues on Windows
+            output_file_js = output_file.as_posix()
+            reporter_path_js = reporter_path.as_posix()
             test_script.write_text(f"""
 // Set env vars BEFORE requiring reporter (matches real Jest behavior)
-process.env.JEST_JUNIT_OUTPUT_FILE = '{output_file}';
+process.env.JEST_JUNIT_OUTPUT_FILE = '{output_file_js}';
 process.env.JEST_JUNIT_CLASSNAME = '{{filepath}}';
 process.env.JEST_JUNIT_SUITE_NAME = '{{filepath}}';
 process.env.JEST_JUNIT_ADD_FILE_ATTRIBUTE = 'true';
 process.env.JEST_JUNIT_INCLUDE_CONSOLE_OUTPUT = 'true';
 
-const Reporter = require('{reporter_path}');
+const Reporter = require('{reporter_path_js}');
 
 // Mock Jest globalConfig
 const globalConfig = {{ rootDir: '/tmp/project' }};