From cac369719843df7372a35827de8082110fd4c556 Mon Sep 17 00:00:00 2001 From: davdhacs <105243888+davdhacs@users.noreply.github.com> Date: Mon, 22 Jun 2026 19:26:23 -0600 Subject: [PATCH 1/2] fix(test): use fixture data for deployment timeline drill-down test MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The "drill down on a pod" test was the only test in deploymentTimeline that used real API data instead of fixture data. When the API returned empty pods (no process events collected yet), the test failed because the timeline list rendered without items — no amount of timeout increase would help since the data simply wasn't there. Switch to fixture data (deploymentEventTimeline.json for the deployment view, podEventTimeline.json for the pod drill-down), consistent with every other test in this file. This tests the UI navigation behavior (drill down shows pod name + back button) without depending on live cluster state. AI-assisted change. Co-Authored-By: Claude Opus 4.6 (1M context) --- .../risk/deploymentTimeline.test.js | 26 ++++++++++--------- 1 file changed, 14 insertions(+), 12 deletions(-) diff --git a/ui/apps/platform/cypress/integration/risk/deploymentTimeline.test.js b/ui/apps/platform/cypress/integration/risk/deploymentTimeline.test.js index a57aebb2eb51f..42eb42d423ecd 100644 --- a/ui/apps/platform/cypress/integration/risk/deploymentTimeline.test.js +++ b/ui/apps/platform/cypress/integration/risk/deploymentTimeline.test.js @@ -142,21 +142,23 @@ describe('Risk Event Timeline for Deployment', () => { describe('Drilling Down To Container Events', () => { it("should drill down on a pod to see that pod's containers", () => { - openEventTimeline(); + openEventTimeline(fixtureForDeploymentEventTimeline); - cy.get(selectors.eventTimeline.timeline.namesList.firstListedName, { - timeout: 30000, - }).then((firstListedName) => { - const firstPodName = firstListedName.text(); + cy.get(selectors.eventTimeline.timeline.namesList.firstListedName).then( + (firstListedName) => { + const firstPodName = firstListedName.text(); - // click the button and drill down to see containers - clickFirstDrillDownButtonInEventTimeline(); + clickFirstDrillDownButtonInEventTimeline( + 'risks/eventTimeline/podEventTimeline.json' + ); - // the back button should be visible - cy.get(selectors.eventTimeline.backButton); - // the pod name should be shown in the panel header - cy.get(selectors.eventTimeline.panelHeader.header).should('contain', firstPodName); - }); + cy.get(selectors.eventTimeline.backButton); + cy.get(selectors.eventTimeline.panelHeader.header).should( + 'contain', + firstPodName + ); + } + ); }); }); From f71fc21f91d6af768f489f41c85c2ffb67a5aae5 Mon Sep 17 00:00:00 2001 From: davdhacs <105243888+davdhacs@users.noreply.github.com> Date: Mon, 22 Jun 2026 19:23:27 -0600 Subject: [PATCH 2/2] fix(ui): stabilize GCR image integration E2E test The GCR test asserts that the "New integration" button does not exist, but does so immediately after page visit without waiting for GCR-specific content to render. On GKE with higher latency, the page may not have fully settled before the assertion runs, causing a consistent failure. Wait for the GCR-specific deprecation notice alert before asserting the button's absence. AI-assisted. Co-Authored-By: Claude Opus 4.6 (1M context) --- .../cypress/integration/integrations/imageIntegrations.test.js | 1 + 1 file changed, 1 insertion(+) diff --git a/ui/apps/platform/cypress/integration/integrations/imageIntegrations.test.js b/ui/apps/platform/cypress/integration/integrations/imageIntegrations.test.js index 0006f334dbf80..2ddfe7ed215c2 100644 --- a/ui/apps/platform/cypress/integration/integrations/imageIntegrations.test.js +++ b/ui/apps/platform/cypress/integration/integrations/imageIntegrations.test.js @@ -229,6 +229,7 @@ describe('Image Integrations', () => { visitIntegrationsTable(integrationSource, integrationType); + cy.get('.pf-v6-c-alert:contains("Deprecation notice")').should('exist'); cy.get('[data-testid="add-integration"]').should('not.exist'); });