Skip to content

test(browser): fix flaky#940

Merged
fi3ework merged 1 commit intomainfrom
max/2026-02-04--05-49PM
Feb 4, 2026
Merged

test(browser): fix flaky#940
fi3ework merged 1 commit intomainfrom
max/2026-02-04--05-49PM

Conversation

@fi3ework
Copy link
Copy Markdown
Member

@fi3ework fi3ework commented Feb 4, 2026

Summary

  • Move temp fixture directories outside of fixtures/ folder to avoid race condition when tests run in parallel

Problem

The browser-mode/watch.test.ts created temp directories inside fixtures/:

  • fixtures/fixtures-test-browser-watch
  • fixtures/fixtures-test-browser-watch-source

When snapshot.test.ts runs in parallel, its prepareFixtures copies the entire fixtures/ directory. If the watch test deletes
its temp directory during this copy operation, it causes ENOENT errors.

Solution

Change paths from:

  • ${__dirname}/fixtures/fixtures-test-browser-watch

To:

  • ${__dirname}/fixtures-test-browser-watch

This matches the pattern used by all other e2e tests.

Related Links

Checklist

  • Tests updated (or not required).
  • Documentation updated (or not required).

Copilot AI review requested due to automatic review settings February 4, 2026 10:27
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adjusts the browser watch-mode e2e tests so that their temporary fixture directories live alongside, rather than inside, the shared fixtures/ directory to avoid cross-test race conditions when tests run in parallel.

Changes:

  • Updated fixturesTargetPath in browser-mode/watch.test.ts to use ${__dirname}/fixtures-test-browser-watch-source and ${__dirname}/fixtures-test-browser-watch, moving them out of the fixtures/ folder.
  • Left the underlying fixture source path (fixturesPath: ${__dirname}/fixtures/watch) unchanged so the same fixture content is copied into the new, sibling temp directories.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@fi3ework fi3ework force-pushed the max/2026-02-04--05-49PM branch 3 times, most recently from eeac60e to 300dcba Compare February 4, 2026 12:04
@fi3ework fi3ework force-pushed the max/2026-02-04--05-49PM branch from 300dcba to dc39dd8 Compare February 4, 2026 12:27
@fi3ework fi3ework merged commit 6fd29f0 into main Feb 4, 2026
9 checks passed
@fi3ework fi3ework deleted the max/2026-02-04--05-49PM branch February 4, 2026 12:49
@9aoy 9aoy mentioned this pull request Feb 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants