NO-JIRA: podImage fix automation testing to remove extra click

[etmurasaki]

No description provided.

[openshift-ci-robot]

@etmurasaki: This pull request explicitly references no jira issue.

Details

In response to this:

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.

[etmurasaki]

/test e2e-monitoring

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 0fc3de0c-3795-47cc-9cd2-b752e278cb02

📥 Commits

Reviewing files that changed from the base of the PR and between 969bc1f and 3b90117.

📒 Files selected for processing (1)

• web/cypress/support/commands/utility-commands.ts

💤 Files with no reviewable changes (1)

• web/cypress/support/commands/utility-commands.ts

---

Walkthrough

The podImage custom Cypress command is simplified by removing a redundant visibility assertion and click operation. The element link is established and clicked in the preceding line, making the subsequent re-query and assertion unnecessary. Downstream logic for scrolling and visibility validation remains intact.

Changes

Cohort / File(s)	Summary
Cypress Utility Commands web/cypress/support/commands/utility-commands.ts	Removed redundant cy.get('@podLink').should('be.visible').click() operation from podImage command after element is already clicked in prior statement.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[openshift-ci]

@etmurasaki: all tests passed!

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.

[zhuje]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: etmurasaki, zhuje

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:

• OWNERS [etmurasaki,zhuje]

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

[etmurasaki]

/label qe-approved