fix(tools): migrate unit test runner from playwright to puppeteer #10982
bennypowerstests.yml
on: pull_request
Matrix: Compile project
SSR Tests (Playwright)
2m 34s
Verify that build runs on Windows
1m 30s
Publish Playwright Report
44s
Validate successful build on main
5s
Annotations
11 errors, 8 warnings, and 1 notice
|
Unit Tests (Web Test Runner)
Process completed with exit code 1.
|
|
elements/pf-v5-chip/test/pf-chip.e2e.ts:14:3 › pf-v5-chip › ssr:
elements/pf-v5-chip/test/pf-chip.e2e.ts#L0
10) elements/pf-v5-chip/test/pf-chip.e2e.ts:14:3 › pf-v5-chip › ssr ──────────────────────────────
Error: browserType.launch: Executable doesn't exist at /ms-playwright/chromium_headless_shell-1217/chrome-headless-shell-linux64/chrome-headless-shell
╔════════════════════════════════════════════════════════╗
║ Looks like Playwright was just updated to 1.59.1. ║
║ Please update docker image as well. ║
║ - current: mcr.microsoft.com/playwright:v1.48.2-noble ║
║ - required: mcr.microsoft.com/playwright:v1.59.1-noble ║
║ ║
║ <3 Playwright Team ║
╚════════════════════════════════════════════════════════╝
|
|
elements/pf-v5-card/test/pf-card.e2e.ts:28:3 › pf-v5-card › ssr hints:
elements/pf-v5-card/test/pf-card.e2e.ts#L0
9) elements/pf-v5-card/test/pf-card.e2e.ts:28:3 › pf-v5-card › ssr hints ─────────────────────────
Error: browserType.launch: Executable doesn't exist at /ms-playwright/chromium_headless_shell-1217/chrome-headless-shell-linux64/chrome-headless-shell
╔════════════════════════════════════════════════════════╗
║ Looks like Playwright was just updated to 1.59.1. ║
║ Please update docker image as well. ║
║ - current: mcr.microsoft.com/playwright:v1.48.2-noble ║
║ - required: mcr.microsoft.com/playwright:v1.59.1-noble ║
║ ║
║ <3 Playwright Team ║
╚════════════════════════════════════════════════════════╝
|
|
elements/pf-v5-card/test/pf-card.e2e.ts:16:3 › pf-v5-card › ssr:
elements/pf-v5-card/test/pf-card.e2e.ts#L0
8) elements/pf-v5-card/test/pf-card.e2e.ts:16:3 › pf-v5-card › ssr ───────────────────────────────
Error: browserType.launch: Executable doesn't exist at /ms-playwright/chromium_headless_shell-1217/chrome-headless-shell-linux64/chrome-headless-shell
╔════════════════════════════════════════════════════════╗
║ Looks like Playwright was just updated to 1.59.1. ║
║ Please update docker image as well. ║
║ - current: mcr.microsoft.com/playwright:v1.48.2-noble ║
║ - required: mcr.microsoft.com/playwright:v1.59.1-noble ║
║ ║
║ <3 Playwright Team ║
╚════════════════════════════════════════════════════════╝
|
|
elements/pf-v5-button/test/pf-button.e2e.ts:14:3 › pf-v5-button › ssr:
elements/pf-v5-button/test/pf-button.e2e.ts#L0
7) elements/pf-v5-button/test/pf-button.e2e.ts:14:3 › pf-v5-button › ssr ─────────────────────────
Error: browserType.launch: Executable doesn't exist at /ms-playwright/chromium_headless_shell-1217/chrome-headless-shell-linux64/chrome-headless-shell
╔════════════════════════════════════════════════════════╗
║ Looks like Playwright was just updated to 1.59.1. ║
║ Please update docker image as well. ║
║ - current: mcr.microsoft.com/playwright:v1.48.2-noble ║
║ - required: mcr.microsoft.com/playwright:v1.59.1-noble ║
║ ║
║ <3 Playwright Team ║
╚════════════════════════════════════════════════════════╝
|
|
elements/pf-v5-banner/test/pf-banner.e2e.ts:14:3 › pf-v5-banner › ssr:
elements/pf-v5-banner/test/pf-banner.e2e.ts#L0
6) elements/pf-v5-banner/test/pf-banner.e2e.ts:14:3 › pf-v5-banner › ssr ─────────────────────────
Error: browserType.launch: Executable doesn't exist at /ms-playwright/chromium_headless_shell-1217/chrome-headless-shell-linux64/chrome-headless-shell
╔════════════════════════════════════════════════════════╗
║ Looks like Playwright was just updated to 1.59.1. ║
║ Please update docker image as well. ║
║ - current: mcr.microsoft.com/playwright:v1.48.2-noble ║
║ - required: mcr.microsoft.com/playwright:v1.59.1-noble ║
║ ║
║ <3 Playwright Team ║
╚════════════════════════════════════════════════════════╝
|
|
elements/pf-v5-badge/test/pf-badge.e2e.ts:14:3 › pf-v5-badge › ssr:
elements/pf-v5-badge/test/pf-badge.e2e.ts#L0
5) elements/pf-v5-badge/test/pf-badge.e2e.ts:14:3 › pf-v5-badge › ssr ────────────────────────────
Error: browserType.launch: Executable doesn't exist at /ms-playwright/chromium_headless_shell-1217/chrome-headless-shell-linux64/chrome-headless-shell
╔════════════════════════════════════════════════════════╗
║ Looks like Playwright was just updated to 1.59.1. ║
║ Please update docker image as well. ║
║ - current: mcr.microsoft.com/playwright:v1.48.2-noble ║
║ - required: mcr.microsoft.com/playwright:v1.59.1-noble ║
║ ║
║ <3 Playwright Team ║
╚════════════════════════════════════════════════════════╝
|
|
elements/pf-v5-background-image/test/pf-background-image.e2e.ts:14:3 › pf-v5-background-image › ssr:
elements/pf-v5-background-image/test/pf-background-image.e2e.ts#L0
4) elements/pf-v5-background-image/test/pf-background-image.e2e.ts:14:3 › pf-v5-background-image › ssr
Error: browserType.launch: Executable doesn't exist at /ms-playwright/chromium_headless_shell-1217/chrome-headless-shell-linux64/chrome-headless-shell
╔════════════════════════════════════════════════════════╗
║ Looks like Playwright was just updated to 1.59.1. ║
║ Please update docker image as well. ║
║ - current: mcr.microsoft.com/playwright:v1.48.2-noble ║
║ - required: mcr.microsoft.com/playwright:v1.59.1-noble ║
║ ║
║ <3 Playwright Team ║
╚════════════════════════════════════════════════════════╝
|
|
elements/pf-v5-back-to-top/test/pf-back-to-top.e2e.ts:14:3 › pf-v5-back-to-top › ssr:
elements/pf-v5-back-to-top/test/pf-back-to-top.e2e.ts#L0
3) elements/pf-v5-back-to-top/test/pf-back-to-top.e2e.ts:14:3 › pf-v5-back-to-top › ssr ──────────
Error: browserType.launch: Executable doesn't exist at /ms-playwright/chromium_headless_shell-1217/chrome-headless-shell-linux64/chrome-headless-shell
╔════════════════════════════════════════════════════════╗
║ Looks like Playwright was just updated to 1.59.1. ║
║ Please update docker image as well. ║
║ - current: mcr.microsoft.com/playwright:v1.48.2-noble ║
║ - required: mcr.microsoft.com/playwright:v1.59.1-noble ║
║ ║
║ <3 Playwright Team ║
╚════════════════════════════════════════════════════════╝
|
|
elements/pf-v5-avatar/test/pf-avatar.e2e.ts:14:3 › pf-v5-avatar › ssr:
elements/pf-v5-avatar/test/pf-avatar.e2e.ts#L0
2) elements/pf-v5-avatar/test/pf-avatar.e2e.ts:14:3 › pf-v5-avatar › ssr ─────────────────────────
Error: browserType.launch: Executable doesn't exist at /ms-playwright/chromium_headless_shell-1217/chrome-headless-shell-linux64/chrome-headless-shell
╔════════════════════════════════════════════════════════╗
║ Looks like Playwright was just updated to 1.59.1. ║
║ Please update docker image as well. ║
║ - current: mcr.microsoft.com/playwright:v1.48.2-noble ║
║ - required: mcr.microsoft.com/playwright:v1.59.1-noble ║
║ ║
║ <3 Playwright Team ║
╚════════════════════════════════════════════════════════╝
|
|
elements/pf-v5-accordion/test/pf-accordion.e2e.ts:14:3 › pf-v5-accordion › ssr:
elements/pf-v5-accordion/test/pf-accordion.e2e.ts#L0
1) elements/pf-v5-accordion/test/pf-accordion.e2e.ts:14:3 › pf-v5-accordion › ssr ────────────────
Error: browserType.launch: Executable doesn't exist at /ms-playwright/chromium_headless_shell-1217/chrome-headless-shell-linux64/chrome-headless-shell
╔════════════════════════════════════════════════════════╗
║ Looks like Playwright was just updated to 1.59.1. ║
║ Please update docker image as well. ║
║ - current: mcr.microsoft.com/playwright:v1.48.2-noble ║
║ - required: mcr.microsoft.com/playwright:v1.59.1-noble ║
║ ║
║ <3 Playwright Team ║
╚════════════════════════════════════════════════════════╝
|
|
Lint files
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Unit Tests (Web Test Runner)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Compile project (22)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Compile project (24)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Validate successful build on main
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-ecosystem/action-add-labels@v1. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Verify that build runs on Windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
SSR Tests (Playwright)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
Publish Playwright Report
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/download-artifact@v4, marocchino/sticky-pull-request-comment@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
🎭 Playwright Run Summary
35 failed
elements/pf-v5-accordion/test/pf-accordion.e2e.ts:14:3 › pf-v5-accordion › ssr ─────────────────
elements/pf-v5-avatar/test/pf-avatar.e2e.ts:14:3 › pf-v5-avatar › ssr ──────────────────────────
elements/pf-v5-back-to-top/test/pf-back-to-top.e2e.ts:14:3 › pf-v5-back-to-top › ssr ───────────
elements/pf-v5-background-image/test/pf-background-image.e2e.ts:14:3 › pf-v5-background-image › ssr
elements/pf-v5-badge/test/pf-badge.e2e.ts:14:3 › pf-v5-badge › ssr ─────────────────────────────
elements/pf-v5-banner/test/pf-banner.e2e.ts:14:3 › pf-v5-banner › ssr ──────────────────────────
elements/pf-v5-button/test/pf-button.e2e.ts:14:3 › pf-v5-button › ssr ──────────────────────────
elements/pf-v5-card/test/pf-card.e2e.ts:16:3 › pf-v5-card › ssr ────────────────────────────────
elements/pf-v5-card/test/pf-card.e2e.ts:28:3 › pf-v5-card › ssr hints ──────────────────────────
elements/pf-v5-chip/test/pf-chip.e2e.ts:14:3 › pf-v5-chip › ssr ────────────────────────────────
elements/pf-v5-clipboard-copy/test/pf-clipboard-copy.e2e.ts:14:3 › pf-v5-clipboard-copy › ssr ──
elements/pf-v5-code-block/test/pf-code-block.e2e.ts:14:3 › pf-v5-code-block › ssr ──────────────
elements/pf-v5-dropdown/test/pf-dropdown.e2e.ts:14:3 › pf-v5-dropdown › ssr ────────────────────
elements/pf-v5-helper-text/test/pf-helper-text.e2e.ts:14:3 › pf-v5-helper-text › ssr ───────────
elements/pf-v5-hint/test/pf-hint.e2e.ts:14:3 › pf-v5-hint › ssr ────────────────────────────────
elements/pf-v5-icon/test/pf-icon.e2e.ts:14:3 › pf-v5-icon › ssr ────────────────────────────────
elements/pf-v5-jump-links/test/pf-jump-links.e2e.ts:14:3 › pf-v5-jump-links › ssr ──────────────
elements/pf-v5-label/test/pf-label.e2e.ts:14:3 › pf-v5-label › ssr ─────────────────────────────
elements/pf-v5-label-group/test/pf-label-group.e2e.ts:14:3 › pf-v5-label-group › ssr ───────────
elements/pf-v5-modal/test/pf-modal.e2e.ts:18:3 › pf-v5-modal › ssr ─────────────────────────────
elements/pf-v5-panel/test/pf-panel.e2e.ts:14:3 › pf-v5-panel › ssr ─────────────────────────────
elements/pf-v5-popover/test/pf-popover.e2e.ts:14:3 › pf-v5-popover › ssr ───────────────────────
elements/pf-v5-progress/test/pf-progress.e2e.ts:14:3 › pf-v5-progress › ssr ────────────────────
elements/pf-v5-progress-stepper/test/pf-progress-stepper.e2e.ts:14:3 › pf-v5-progress-stepper › ssr
elements/pf-v5-search-input/test/pf-search-input.e2e.ts:14:3 › pf-v5-search-input › ssr ────────
elements/pf-v5-select/test/pf-select.e2e.ts:14:3 › pf-v5-select › ssr ──────────────────────────
elements/pf-v5-spinner/test/pf-spinner.e2e.ts:14:3 › pf-v5-spinner › ssr ───────────────────────
elements/pf-v5-switch/test/pf-switch.e2e.ts:14:3 › pf-v5-switch › ssr ──────────────────────�
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
test-report
|
244 KB |
sha256:1a1ae4b8b50440fd487c1a8e5205e454025a122494b1c718c8c7c6470df7d3b1
|
|