Skip to content

[release-4.19] OCPBUGS-100307: Re-enable Knative Cypress e2e tests - #16906

Open
cajieh wants to merge 1 commit into
openshift:release-4.19from
cajieh:OCPBUGS-100307-release-4.19-re-enable-knative
Open

[release-4.19] OCPBUGS-100307: Re-enable Knative Cypress e2e tests#16906
cajieh wants to merge 1 commit into
openshift:release-4.19from
cajieh:OCPBUGS-100307-release-4.19-re-enable-knative

Conversation

@cajieh

@cajieh cajieh commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Analysis / Root cause:
Knative Cypress e2e was disabled under OCPBUGS-99226 (#16782) because knative-ci.feature was flaking in CI. Failures commonly hit the beforeEachcy.initAdmin() path when the perspective switcher was not ready yet (timeout on perspective-switcher-toggle / menu interaction), which blocked unrelated PRs.

The harness was also using fixed cy.wait() delays around perspective menu open, which is brittle under React 18 / CI load.

Solution description:
Re-enable Knative Cypress suites and harden shared perspective-switcher helpers:

  1. Re-enable Knative runs in:
    • frontend/integration-tests/test-cypress.sh (test-cypress-knative-nightly, test-cypress-knative-headless)
    • test-prow-e2e.sh (SCENARIO == knative)
  2. In initAdmin / initDeveloper, wait for perspective-switcher-toggle to exist and be visible (60s) before switching perspective.
  3. In nav.ts perspective switcher helpers:
    • Increase menu aria-expanded wait where needed
    • Replace fixed cy.wait(1000/1500) with waiting for perspective-switcher-menu-option visibility
    • Use a normal .click() (no force: true) once the option is visible

No product UI changes; test harness / CI wiring only.

Screenshots / screen recording:
N/A — CI / Cypress harness change only.

Test setup:

  • Cluster with Knative / Serverless available (same as existing knative Cypress jobs)
  • Local (optional): from frontend/, run knative headless suite via ./integration-tests/test-cypress.sh -p knative -h true against a configured bridge/cluster
  • CI: confirm knative scenario / nightly + headless jobs run and are green on this PR

Test cases:

  1. Knative prow scenario (SCENARIO=knative) executes (no longer skipped/commented out).
  2. Nightly / headless Cypress aggregators invoke knative suites again.
  3. Knative beforeEach / initAdmin no longer times out waiting for perspective switcher under CI load.
  4. Switching to Core platform and Developer perspectives succeeds without forced clicks or fixed sleeps.
  5. knative-ci.feature smoke scenarios pass (create / interact with knative service & revision as covered by the suite).
  6. Unrelated Cypress packages that use initAdmin / initDeveloper still pass (shared harness change).

Browser conformance:

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

N/A for merge gate (CI Cypress / Chrome-like headless). Mark browsers only if manually exercised locally.

Additional info:

Reviewers and assignees:
/assign

Summary by CodeRabbit

  • Tests
    • Enabled Knative Cypress suites for both nightly and headless runs.
    • Re-enabled Knative Cypress execution when the end-to-end scenario is set to Knative.
    • Improved reliability of perspective-switching tests by replacing fixed waits with UI readiness checks (waiting for the correct legacy toggle and menu options to become visible before interacting).

Manual backport of openshift#16889 for release-4.19. Package path is
integration-tests-cypress (not integration-tests). Re-enable knative
Cypress suites and harden perspective-switcher waits in initAdmin/nav.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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 openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 4, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@cajieh: This pull request references Jira Issue OCPBUGS-100307, which is invalid:

  • expected the bug to target either version "4.19." or "openshift-4.19.", but it targets "4.22.0" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Verified instead
  • expected dependent Jira Issue OCPBUGS-99292 to target a version in 4.20.0, 4.20.z, but it targets "5.0.0" instead

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:

Summary

  • Re-enable Knative Cypress suites for both nightly and headless runs
  • Re-enable Knative Cypress execution when the end-to-end scenario is set to Knative
  • Improve reliability of perspective-switching tests by replacing fixed waits with UI readiness checks

Analysis / Root cause:
Knative Cypress e2e was disabled under OCPBUGS-99226 (#16782) because knative-ci.feature was flaking in CI. Failures commonly hit the beforeEachcy.initAdmin() path when the perspective switcher was not ready yet (timeout on perspective-switcher-toggle / menu interaction).

Solution description:
Re-enable Knative Cypress suites and harden shared perspective-switcher helpers:

  1. Re-enable Knative runs in:
  • frontend/integration-tests/test-cypress.sh (test-cypress-knative-nightly, test-cypress-knative-headless)
  • test-prow-e2e.sh (SCENARIO == knative)
  1. In initAdmin / initDeveloper, wait for perspective-switcher-toggle to exist and be visible (60s) before switching perspective.
  2. In nav.ts perspective switcher helpers:
  • Add should('be.visible') wait with timeout before clicking menu options
  • Use a normal .click() (no force: true) once the option is visible

No product UI changes; test harness / CI wiring only.

Test plan

  • Knative prow scenario (SCENARIO=knative) executes (no longer skipped/commented out)
  • Nightly / headless Cypress aggregators invoke knative suites again
  • Knative beforeEach / initAdmin no longer times out waiting for perspective switcher under CI load

Additional info:

🤖 Generated with Claude Code

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

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: 509d7a38-8359-46b4-87fc-47c4aed24e1a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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

@openshift-ci
openshift-ci Bot requested review from jhadvig and spadgett August 4, 2026 15:33
@openshift-ci openshift-ci Bot added the kind/cypress Related to Cypress e2e integration testing label Aug 4, 2026
@rhamilto

rhamilto commented Aug 4, 2026

Copy link
Copy Markdown
Member

/approve
/label backport-risk-assessed
/lgtm
/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Aug 4, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@rhamilto: This PR has been marked as verified by CI.

Details

In response to this:

/approve
/label backport-risk-assessed
/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-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Aug 4, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 4, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

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

@openshift-ci

openshift-ci Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cajieh, 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:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 4, 2026
@rhamilto

rhamilto commented Aug 5, 2026

Copy link
Copy Markdown
Member

/test e2e-gcp-console

1 similar comment
@rhamilto

rhamilto commented Aug 5, 2026

Copy link
Copy Markdown
Member

/test e2e-gcp-console

@openshift-ci

openshift-ci Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

@cajieh: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-console c3500f7 link true /test e2e-gcp-console

Full PR test history. Your PR dashboard.

Details

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 kubernetes-sigs/prow repository. I understand the commands that are listed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. kind/cypress Related to Cypress e2e integration testing lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants