chore(e2e): update existing scorecard e2e

[HusneShabbir]

PR Description

Title: Migrate Scorecard E2E tests from mocked to real backend

Which issue(s) does this PR fix

Fixes RHIDP-10938

Summary

Replaced mocked API responses with real-time backend integration for scorecard plugin tests.

What Changed

• Real backend testing - Tests now validate against live scorecard API instead of mocked responses
• New tests - Added single scorecard visibility tests (GitHub-only, Jira-only)
• Refactored - Added importAndOpenScorecard() helper to reduce code duplication
• Cleanup - Removed unused mock utilities and methods

Deleted Files

• scorecard-utils.ts
• scorecard-response-utils.ts

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-3921
• quay.io/rhdh-community/rhdh:pr-3921-f6707165

/test e2e-ocp-helm

[HusneShabbir]

/retest

[christoph-jerolimov]

Hi @HusneShabbir thanks for this PR. I'm sorry but the current (old?) scorecard tests are so flaky that I disabled them with #3925 again.

I created ticket https://issues.redhat.com/browse/RHDHBUGS-2444 for this. Can you pick this up and solve this with this issue here together?

But for that, you must of course re-enable the tests (again) and imho the tests should pass 3, better 5, times. So I mark this on hold until someone verified that this here is really an improvement OR we improved and re-eanbled the tests with another PR. Without running the tests I don't think we should merge this.

/hold

[HusneShabbir]

/retest

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-3921
• quay.io/rhdh-community/rhdh:pr-3921-93284bef

/test e2e-ocp-helm

[HusneShabbir]

/retest

[christoph-jerolimov]

The flakyness is fixed but it looks like you need to rebase your PR and fix the updated tests.

Feel free to remove the hold when it passes.

[HusneShabbir]

/retest

[HusneShabbir]

/retest

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-3921
• quay.io/rhdh-community/rhdh:pr-3921-d7172655

/test e2e-ocp-helm

[HusneShabbir]

/retest

[HusneShabbir]

/retest

[HusneShabbir]

/retest

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign subhashkhileri for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• .ibm/OWNERS
• e2e-tests/OWNERS

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

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-3921
• quay.io/rhdh-community/rhdh:pr-3921-31561091

/test e2e-ocp-helm

[HusneShabbir]

/retest

[HusneShabbir]

/retest

[github-actions]

This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 21 days.

[github-actions]

This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 21 days.

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-3921
• quay.io/rhdh-community/rhdh:pr-3921-b6527ec5

[HusneShabbir]

/retest

[HusneShabbir]

/retest

[github-actions]

🚫 Image Push Skipped.

The container image push was skipped because the build was skipped (either due to [skip-build] tag or no relevant changes with existing image)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[openshift-ci]

@HusneShabbir: 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-ocp-helm	f4d60fc	link	true	/test e2e-ocp-helm

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.