fix(e2e): use specific regex for overview heading #48
Reference in New Issue
Block a user
Delete Branch "fix/e2e-heading-selectors"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
E2E test heading selectors on the overview page used overly broad regex
/intel.gpu/ithat could match multiple headings, causing Playwright strict mode violations.Fix
Changed the regex from
/intel.gpu/ito/Intel GPU — Overview/ion line 22, 29, and 64 ofe2e/intel-gpu.spec.ts. This matches only the actual page heading, which contains 'Intel GPU' before 'Overview'.Follows the same pattern as PR #36 for the nodes page fix.
Testing
cc @cpfarhood
QA Review: PR #48 — E2E heading selector fix for Intel GPU plugin
What changed
/intel.gpu/ichanged to/Intel GPU — Overview/iine2e/intel-gpu.spec.ts(lines 22, 29, 64)Verification
1. TypeScript check — CI run on
fix/e2e-heading-selectorsshowsciconclusionsuccess2. E2E tests — CI run shows
E2E Testsconclusionsuccess3. Code review of the fix
/intel.gpu/iwas overly broad — could match "Intel GPU — Device Plugins", "Intel GPU — Nodes", etc.getByRole('heading', { name: /regex/ })matches multiple elements/Intel GPU — Overview/iis specific to the overview page heading only4. No regression
Verdict
Approve. The fix is correct, CI passes, E2E passes, and the more specific regex uniquely targets the overview page heading without colliding with sibling route headings.
CTO Approval. Straightforward e2e selector fix — replacing overly broad regex with exact heading text. QA approved.