Repository navigation
Conversation
…provider - Mark both Quick Access content tests test.fixme when IS_OPENSHIFT=false. The /developer-hub proxy target (test-backstage-customization-provider) is OpenShift-only, so AKS/GKE render the card's "Could not fetch data." state. Tracked in RHDHBUGS-4096; the previous RHDHBUGS-3950 was closed without restoring the coverage. - Deploy test-backstage-customization-provider in the OCP upgrade lane, which never provisioned it and left /api/proxy/developer-hub answering 503. Assisted-by: OpenCode
PR Summary by QodoFix Quick Access E2E coverage in Kubernetes and OCP upgrade lanes
AI Description
Diagram
High-Level Assessment
Files changed (3)
|
|
Code Review by QodoView low (1) 1. Provider deploy failure in upgrade lane goes unnoticed
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5794 +/- ##
==========================================
- Coverage 78.65% 72.94% -5.71%
==========================================
Files 67 60 -7
Lines 726 573 -153
Branches 100 83 -17
==========================================
- Hits 571 418 -153
Misses 154 154
Partials 1 1
*This pull request uses carry forward flags. Click here to find out more.
Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
|
/test e2e-ocp-helm-upgrade-nightly |



Description
The two Quick Access content tests fail on
showcase-k8s(AKS/GKE, helm and operator) and in the OCP upgrade lane. The homepage renders and the Quick Access card is present, but shows itsError: Could not fetch data.state because the/developer-hubproxy target (test-backstage-customization-provider) is unreachable:# Doesn't work on K8s), and on AKS/GKEK8S_CLUSTER_ROUTER_BASEis a raw IP, so the target is not even a valid URL (skipped configuring /developer-hub due to Proxy target is not a valid URL).handle_ocp_helm_upgradenever deployed the provider, soGET /api/proxy/developer-hubreturned 503.Both are pre-existing and affect
maintoday. Not a product bug.Changes
test.fixmewhenIS_OPENSHIFT === "false"— they are known-broken on Kubernetes, not deliberately skipped.test-backstage-customization-providerin the OCP upgrade lane right afterinitiate_upgrade_base_deployments, so the build finishes while the baseline RHDH waits for readiness.Which issue(s) does this PR fix
Jira: https://redhat.atlassian.net/browse/RHDHBUGS-4096
RHDHBUGS-3950 covered the Kubernetes part but was closed without restoring the coverage.
How to test changes / Special notes to the reviewer
yarn lint,yarn fmt:check,yarn test:unit(238 passed),shellcheckonupgrade.sh.showcasewhere the provider is deployed.release-2.1PR: [release-2.1] fix(e2e): mark Quick Access fixme on Kubernetes and seed the upgrade provider #5793