Repository navigation
fix(ui): use fixture data in podTimeline E2E tests - #21341
Conversation
All 16 tests in podTimeline.test.js fail on GKE because the deployment-level event timeline renders empty (no process events collected on a fresh cluster), so the drill-down button never appears. Pass deploymentEventTimeline.json fixture to openEventTimeline() for every test, matching the pattern used in deploymentTimeline.test.js. Also pass podEventTimeline.json fixture to the Legend test's drill-down call for consistency. AI-assisted change. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
Skipping CI for Draft Pull Request. |
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The previous fix waited for a deprecation notice alert that may not be rendered in time. Wait for the IntegrationsTable "results found" h2 instead, which confirms the table component (and its button visibility logic) has rendered. AI-assisted change. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
🚀 Build Images ReadyImages are ready for commit 87be932. To use with deploy scripts: export MAIN_IMAGE_TAG=4.12.x-546-g87be932172 |
Description
All 16 tests in
podTimeline.test.jsfail on GKE becauseopenEventTimeline()callsviewGraph()without a fixture, so the deployment-level event timeline hits the live API. On a fresh cluster with no process events collected, the timeline renders empty and the drill-down button ([data-testid="timeline-drill-down-button"]) never appears.Fix: pass
deploymentEventTimeline.jsonfixture toopenEventTimeline()in every test, matching the pattern used indeploymentTimeline.test.js(fixed in #21338). Also passpodEventTimeline.jsonto the Legend test's drill-down call for full fixture coverage.User-facing documentation
Testing and quality
Automated testing
How I validated my change
Same pattern as the
deploymentTimeline.test.jsfix in #21338 which is passing on GKE. TheopenEventTimeline()function now accepts and forwards a fixture path toviewGraph(), so the deployment-level GraphQL response is intercepted with fixture data instead of relying on live API data that doesn't exist on a fresh cluster.