[Pavel Feldman (pavelfeldman)]

The extension workflow now uploads packages/extension/dist as the artifact playwright-extension, right after the build.

• Each run on a PR or on main that touches the extension has a downloadable build. The archive is the extension itself: extract it and load it unpacked.
• The upload runs before the tests, so the build is available when tests fail too.
• The content is the same directory that publish_extension.yml zips for the Chrome Web Store.

[github-actions]

Test results for "tests 1"

1 flaky

⚠️ [installation tests] › connect-to-selenium.spec.ts:20 › connect to selenium `@package-installations-ubuntu-latest`

23627 passed, 713 skipped

---

Merge workflow run.

[github-actions]

Test results for "MCP"

3 failed
❌ [chrome] › mcp/crash.spec.ts:31 › crash recovery › reports the navigation error, then resets and logs the crash @mcp-ubuntu-latest-chrome
❌ [chrome] › mcp/crash.spec.ts:58 › crash recovery › lists only one tab @mcp-ubuntu-latest-chrome
❌ [chrome] › mcp/crash.spec.ts:79 › crash recovery › marks non-current crashed tab in the tab list @mcp-ubuntu-latest-chrome

5232 passed, 631 skipped

---

Merge workflow run.

[microsoft-playwright-automation]

🟢 The three failures pre-date this PR

Hi, I'm the Playwright bot. I checked the MCP failures; this PR did not cause them.

Details

Covers MCP run 43293609204 at 21aba0e83491788695b569326b886c40f8ae3f10, reported in this comment.

The entire diff adds an artifact upload to .github/workflows/tests_extension.yml. It changes neither the MCP workflow nor the tests, helpers, or browser code these tests exercise.

Pre-existing flake / infra

All three [chrome] tests in tests/mcp/crash.spec.ts also failed in the earlier main run 43284830655, at 9a82788d83cf91d8262e65a432b9bf93dc5418a7, with the same errors:

• :31 — reports the navigation error, then resets and logs the crash: 30-second timeout at the recovery check, line 48.
• :58 — lists only one tab: 30-second timeout and Not connected at line 71.
• :79 — marks non-current crashed tab in the tab list: 30-second timeout and Not connected at line 93.

This confirms that the failures existed without this PR. It does not establish their root cause or whether they are intermittent.

The tests 1 report has no failed tests; its Selenium test passed on retry.

_{Checked the failures on Linux by the Playwright bot - agent run}