OCPBUGS-105519: Fix flaky e2e tests missing warmupSPA

[rhamilto]

Analysis / Root cause:

Multiple Playwright e2e test suites intermittently fail because the SPA session is not established before navigating to deep URLs. The page gets stuck on the OAuth login screen, and downstream locators (e.g. actions-menu-button, fit-to-screen) time out because they never appear on the login page.

Affected suites:

• webterminal/web-terminal-config.spec.ts
• knative/serverless/knative-ci.spec.ts

Both suites navigate directly to deep URLs via goTo() without first warming up the SPA. The Playwright browser context has saved storage state (cookies/tokens from the auth setup project), but the first navigation to a deep URL can land on the OAuth login page if the session has not been fully established in the browser context.

Every other working test suite calls warmupSPA(page) in beforeEach to navigate to / first and confirm the sidebar is visible, which ensures the auth redirect completes and the SPA is ready before deep navigation.

Solution description:

Added test.beforeEach hooks that call warmupSPA(page) in both test suites, matching the pattern used by all other test suites.

Screenshots / screen recording:

Test setup:
Run the affected Playwright e2e test suites against a cluster.

Test cases:

• All web-terminal-config.spec.ts tests pass consistently
• All knative-ci.spec.ts tests pass consistently
• Tests no longer hang at the login page

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:
Jira: https://redhat.atlassian.net/browse/OCPBUGS-105519

Reviewers and assignees:

Summary by CodeRabbit

• Bug Fixes

  • Improved node scheduling messages with accurate singular and plural wording.
  • Corrected translation extraction for pluralized localization keys.

• Tests

  • Improved web terminal configuration test reliability by warming up the application before each test.
  • Improved Knative CI test reliability by warming up the application before each test.
  • Added consistent application startup preparation across these test scenarios to reduce failures caused by incomplete loading.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[openshift-ci-robot]

@rhamilto: This pull request references Jira Issue OCPBUGS-105519, which is invalid:

• expected the bug to target the "5.0.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Analysis / Root cause:

The webterminal/web-terminal-config.spec.ts Playwright e2e tests intermittently fail because the SPA session is not established before navigating to deep URLs. All tests in the suite fail with the same downstream error — actions-menu-button not visible — because the page is stuck on the OAuth login screen.

The test suite navigates directly to /k8s/cluster/operator.openshift.io~v1~Console/cluster via goTo() without first warming up the SPA. The Playwright browser context has saved storage state (cookies/tokens from the auth setup project), but the first navigation to a deep URL can land on the OAuth login page if the session has not been fully established in the browser context.

Every other working test suite calls warmupSPA(page) in beforeEach to navigate to / first and confirm the sidebar is visible, which ensures the auth redirect completes and the SPA is ready before deep navigation.

Solution description:

Added a test.beforeEach hook that calls warmupSPA(page), matching the pattern used by all other test suites.

Screenshots / screen recording:

Test setup:
Run the web-terminal-config.spec.ts Playwright e2e tests against a cluster with the Web Terminal Operator installed.

Test cases:

• All web-terminal-config.spec.ts tests pass consistently
• Tests no longer hang at the login page

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:
Jira: https://redhat.atlassian.net/browse/OCPBUGS-105519

Reviewers and assignees:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 3a88d9fc-cea5-4533-a792-bdd18c4d23d3

📥 Commits

Reviewing files that changed from the base of the PR and between c68a53c and 21f23c1.

📒 Files selected for processing (7)

• dynamic-demo-plugin/i18next.config.ts
• dynamic-demo-plugin/package.json
• frontend/e2e/tests/knative/serverless/knative-ci.spec.ts
• frontend/e2e/tests/webterminal/web-terminal-config.spec.ts
• frontend/i18next.config.ts
• frontend/packages/console-app/locales/en/console-app.json
• frontend/packages/console-app/src/components/nodes/useCustomNodeActions.tsx

🚧 Files skipped from review as they are similar to previous changes (1)

• frontend/e2e/tests/webterminal/web-terminal-config.spec.ts

---

Walkthrough

The changes update i18next extraction and node scheduling pluralization, build the dynamic plugin SDK directly, and warm up the SPA before tests in the web terminal and Knative CI suites.

Changes

Localization and node scheduling messages

Layer / File(s)	Summary
Pluralized node scheduling localization dynamic-demo-plugin/i18next.config.ts, frontend/i18next.config.ts, frontend/packages/console-app/locales/en/console-app.json, frontend/packages/console-app/src/components/nodes/useCustomNodeActions.tsx	i18next extraction removes _one and _other suffixes. Node scheduling messages use count with singular and plural entries.
Dynamic plugin SDK build wiring dynamic-demo-plugin/package.json	The plugin builds the SDK directly from its package directory. The separate SDK installation script was removed.
SPA warmup in E2E setup frontend/e2e/tests/webterminal/web-terminal-config.spec.ts, frontend/e2e/tests/knative/serverless/knative-ci.spec.ts	Both suites invoke warmupSPA(page) before each test.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• openshift/console#16741: Modifies the BasePage implementation used by warmupSPA.
• openshift/console#16926: Updates related i18next configuration and pluralization keys.
• openshift/console#16940: Adds warmupSPA calls to Playwright E2E tests.

Suggested labels: lgtm

Suggested reviewers: cajieh, jhadvig, logonoff

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the Jira issue and the primary fix for flaky e2e tests caused by missing warmupSPA calls.
Description check	✅ Passed	The description explains the root cause, solution, setup, affected tests, and validation steps; non-critical reviewer and browser fields remain incomplete.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The PR only adds warmupSPA hooks to the two Playwright suites; all inspected test() and test.describe() titles are literal, static strings with no dynamic values.
Test Structure And Quality	✅ Passed	The check targets Ginkgo tests, but the PR changes TypeScript Playwright suites using test.describe/test.beforeEach; no Go or Ginkgo test files are changed.
Microshift Test Compatibility	✅ Passed	The PR adds Playwright hooks only; no new Ginkgo It/Describe/Context/When tests are present, so the MicroShift compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The PR adds no Ginkgo e2e tests or Go files; it changes existing Playwright TypeScript hooks and i18n files only, so SNO multi-node compatibility checks do not apply.
Topology-Aware Scheduling Compatibility	✅ Passed	The PR changes only Playwright setup, i18next configuration, package scripts, and UI translation keys. It adds no deployment, operator, controller, or scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The effective patch changes only TypeScript, JSON, and package metadata; it adds no OTE binary, process-level setup, or stdout write.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The PR adds only Playwright warmup hooks. It adds no Ginkgo tests, IPv4 assumptions, or external-network calls.
No-Weak-Crypto	✅ Passed	The seven-file PR adds SPA hooks and i18n/package changes only; added-line review found no MD5/SHA-1/DES/RC4/Blowfish/ECB, custom crypto, or secret comparisons.
Container-Privileges	✅ Passed	The PR changes seven non-container files; no added line contains privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	The PR adds no logging calls. The new test hook only calls warmupSPA, which navigates to / and checks UI visibility; no passwords, tokens, PII, or customer data are logged.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[rhamilto]

/jira refresh

[openshift-ci-robot]

@rhamilto: This pull request references Jira Issue OCPBUGS-105519, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

/jira refresh

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@rhamilto: This pull request references Jira Issue OCPBUGS-105519, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

Analysis / Root cause:

The webterminal/web-terminal-config.spec.ts Playwright e2e tests intermittently fail because the SPA session is not established before navigating to deep URLs. All tests in the suite fail with the same downstream error — actions-menu-button not visible — because the page is stuck on the OAuth login screen.

The test suite navigates directly to /k8s/cluster/operator.openshift.io~v1~Console/cluster via goTo() without first warming up the SPA. The Playwright browser context has saved storage state (cookies/tokens from the auth setup project), but the first navigation to a deep URL can land on the OAuth login page if the session has not been fully established in the browser context.

Every other working test suite calls warmupSPA(page) in beforeEach to navigate to / first and confirm the sidebar is visible, which ensures the auth redirect completes and the SPA is ready before deep navigation.

Solution description:

Added a test.beforeEach hook that calls warmupSPA(page), matching the pattern used by all other test suites.

Screenshots / screen recording:

Test setup:
Run the web-terminal-config.spec.ts Playwright e2e tests against a cluster with the Web Terminal Operator installed.

Test cases:

• All web-terminal-config.spec.ts tests pass consistently
• Tests no longer hang at the login page

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:
Jira: https://redhat.atlassian.net/browse/OCPBUGS-105519

Reviewers and assignees:

Summary by CodeRabbit

• Tests
• Improved web terminal configuration test reliability by warming up the application before each test.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[logonoff]

/lgtm

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console
/test e2e-playwright

[openshift-ci-robot]

@rhamilto: This pull request references Jira Issue OCPBUGS-105519, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Analysis / Root cause:

Multiple Playwright e2e test suites intermittently fail because the SPA session is not established before navigating to deep URLs. The page gets stuck on the OAuth login screen, and downstream locators (e.g. actions-menu-button, fit-to-screen) time out because they never appear on the login page.

Affected suites:

• webterminal/web-terminal-config.spec.ts
• knative/serverless/knative-ci.spec.ts

Both suites navigate directly to deep URLs via goTo() without first warming up the SPA. The Playwright browser context has saved storage state (cookies/tokens from the auth setup project), but the first navigation to a deep URL can land on the OAuth login page if the session has not been fully established in the browser context.

Every other working test suite calls warmupSPA(page) in beforeEach to navigate to / first and confirm the sidebar is visible, which ensures the auth redirect completes and the SPA is ready before deep navigation.

Solution description:

Added test.beforeEach hooks that call warmupSPA(page) in both test suites, matching the pattern used by all other test suites.

Screenshots / screen recording:

Test setup:
Run the affected Playwright e2e test suites against a cluster.

Test cases:

• All web-terminal-config.spec.ts tests pass consistently
• All knative-ci.spec.ts tests pass consistently
• Tests no longer hang at the login page

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:
Jira: https://redhat.atlassian.net/browse/OCPBUGS-105519

Reviewers and assignees:

Summary by CodeRabbit

• Tests
• Improved web terminal configuration test reliability by warming up the application before each test.
• Improved Knative CI test reliability by warming up the application before each test.
• Added consistent application startup preparation across these test scenarios to reduce failures caused by incomplete loading.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[logonoff]

/lgtm

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console
/test e2e-playwright

[logonoff]

/lgtm cancel

eslint warnings

[logonoff]

/lgtm
/verified by ci

[openshift-ci-robot]

@logonoff: This PR has been marked as verified by ci.

Details

In response to this:

/lgtm
/verified by ci

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console
/test e2e-playwright

[openshift-ci-robot]

@rhamilto: This pull request references Jira Issue OCPBUGS-105519, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

Analysis / Root cause:

Multiple Playwright e2e test suites intermittently fail because the SPA session is not established before navigating to deep URLs. The page gets stuck on the OAuth login screen, and downstream locators (e.g. actions-menu-button, fit-to-screen) time out because they never appear on the login page.

Affected suites:

• webterminal/web-terminal-config.spec.ts
• knative/serverless/knative-ci.spec.ts

Both suites navigate directly to deep URLs via goTo() without first warming up the SPA. The Playwright browser context has saved storage state (cookies/tokens from the auth setup project), but the first navigation to a deep URL can land on the OAuth login page if the session has not been fully established in the browser context.

Every other working test suite calls warmupSPA(page) in beforeEach to navigate to / first and confirm the sidebar is visible, which ensures the auth redirect completes and the SPA is ready before deep navigation.

Solution description:

Added test.beforeEach hooks that call warmupSPA(page) in both test suites, matching the pattern used by all other test suites.

Screenshots / screen recording:

Test setup:
Run the affected Playwright e2e test suites against a cluster.

Test cases:

• All web-terminal-config.spec.ts tests pass consistently
• All knative-ci.spec.ts tests pass consistently
• Tests no longer hang at the login page

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:
Jira: https://redhat.atlassian.net/browse/OCPBUGS-105519

Reviewers and assignees:

Summary by CodeRabbit

• Bug Fixes

• Improved node scheduling messages with accurate singular and plural wording.

• Corrected translation extraction for pluralized localization keys.

• Tests

• Improved web terminal configuration test reliability by warming up the application before each test.

• Improved Knative CI test reliability by warming up the application before each test.

• Added consistent application startup preparation across these test scenarios to reduce failures caused by incomplete loading.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD 42ca40a and 2 for PR HEAD 21f23c1 in total

[logonoff]

/test analyze frontend

[logonoff]

try to force push to invalidate weird and broken build cache:

/lgtm
/verified by ci

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff, rhamilto

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• dynamic-demo-plugin/OWNERS [logonoff,rhamilto]
• frontend/OWNERS [logonoff,rhamilto]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci-robot]

@logonoff: This PR has been marked as verified by ci.

Details

In response to this:

try to force push to invalidate weird and broken build cache:

/lgtm
/verified by ci

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-merge-bot]

Scheduling tests matching the pipeline_run_if_changed or not excluded by pipeline_skip_if_only_changed parameters:
/test e2e-gcp-console
/test e2e-playwright

[logonoff]

/test analyze backend frontend images okd-scos-images

[openshift-ci-robot]

@rhamilto: Jira Issue Verification Checks: Jira Issue OCPBUGS-105519
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-105519 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Analysis / Root cause:

Multiple Playwright e2e test suites intermittently fail because the SPA session is not established before navigating to deep URLs. The page gets stuck on the OAuth login screen, and downstream locators (e.g. actions-menu-button, fit-to-screen) time out because they never appear on the login page.

Affected suites:

• webterminal/web-terminal-config.spec.ts
• knative/serverless/knative-ci.spec.ts

Both suites navigate directly to deep URLs via goTo() without first warming up the SPA. The Playwright browser context has saved storage state (cookies/tokens from the auth setup project), but the first navigation to a deep URL can land on the OAuth login page if the session has not been fully established in the browser context.

Every other working test suite calls warmupSPA(page) in beforeEach to navigate to / first and confirm the sidebar is visible, which ensures the auth redirect completes and the SPA is ready before deep navigation.

Solution description:

Added test.beforeEach hooks that call warmupSPA(page) in both test suites, matching the pattern used by all other test suites.

Screenshots / screen recording:

Test setup:
Run the affected Playwright e2e test suites against a cluster.

Test cases:

• All web-terminal-config.spec.ts tests pass consistently
• All knative-ci.spec.ts tests pass consistently
• Tests no longer hang at the login page

Browser conformance:

• Chrome
• Firefox
• Safari (or Epiphany on Linux)

Additional info:
Jira: https://redhat.atlassian.net/browse/OCPBUGS-105519

Reviewers and assignees:

Summary by CodeRabbit

• Bug Fixes

• Improved node scheduling messages with accurate singular and plural wording.

• Corrected translation extraction for pluralized localization keys.

• Tests

• Improved web terminal configuration test reliability by warming up the application before each test.

• Improved Knative CI test reliability by warming up the application before each test.

• Added consistent application startup preparation across these test scenarios to reduce failures caused by incomplete loading.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-merge-robot]

Fix included in release 5.0.0-0.nightly-2026-08-11-071938