Open Bug 2026715 Opened 6 months ago Updated 5 months ago

[firefox-devtools-mcp] Windows: Vitest fork issues with Firefox integration tests

Categories

(Developer Infrastructure :: Firefox MCP, task, P3)

Product:
Developer Infrastructure
Component:
Firefox MCP
Type:
task

Tracking

(Not tracked)

People

(Reporter: jdescottes, Unassigned)

Details

(cloned from https://github.com/mozilla/firefox-devtools-mcp/issues/33)

Problem

Vitest has known issues with process forking on Windows when running integration tests that spawn Firefox. The tests hang or fail unpredictably due to how vitest isolates test processes.

Related upstream issues:

Current Workaround

We use a separate test runner (scripts/run-integration-tests-windows.mjs) that runs integration tests directly via Node.js without vitest's process isolation.

The CI workflow detects Windows and automatically uses this runner instead of vitest for integration tests. Unit tests still run via vitest on all platforms.

Ideal Solution

Once vitest fixes the underlying forking issues on Windows, we should:

  1. Remove the separate Windows test runner
  2. Use vitest for all tests on all platforms

Labels

  • platform: windows
  • type: workaround
Summary: [firefox-devtoos-mcp] Windows: Vitest fork issues with Firefox integration tests → [firefox-devtools-mcp] Windows: Vitest fork issues with Firefox integration tests
Component: AI for Development → Firefox MCP
No longer blocks: firefox-devtools-mcp
You need to log in before you can comment on or make changes to this bug.