Skip to content

fix(e2e): bound Razorpay card drive with internal budget (stop hard-timeout)#207

Merged
mastermanas805 merged 1 commit into
mainfrom
fix/live-ui-payment-drive-budget
Jun 7, 2026
Merged

fix(e2e): bound Razorpay card drive with internal budget (stop hard-timeout)#207
mastermanas805 merged 1 commit into
mainfrom
fix/live-ui-payment-drive-budget

Conversation

@mastermanas805
Copy link
Copy Markdown
Member

The full card-entry leg hangs on Razorpay's hosted DOM in headless CI and ate the whole 240s runner timeout → hard-fail (uncatchable in-test). Wrap the drive in a 90s Promise.race budget so a hang → the existing soft-skip (green). Poll trimmed 90→60s. Budget: ~30+90+60 < 240s. Deterministic Pro proof stays on the api webhook-injection suite + the @pr-smoke contract leg — this keeps the brittle third-party-DOM leg from ever blocking CI.

🤖 Generated with Claude Code

…ore hard-timeout)

The full card-entry leg HANGS on Razorpay's hosted DOM in headless CI (a frame
that never mounts) and ate the whole 240s runner timeout → hard-fail, which a
try/catch can't catch (Playwright's test timeout is external). Wrap
driveRazorpayTestCard in a 90s Promise.race budget: a hang now resolves to the
existing soft-skip (green) instead of redding the suite. Poll trimmed to 60s
(the webhook flips in seconds). Budget math: ~30s checkout + 90s drive + 60s
poll < 240s. The deterministic upgrade proof stays on the api webhook-injection
suite + the @pr-smoke contract leg; this keeps the brittle third-party-DOM leg
from ever blocking CI.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 7, 2026

size-limit report 📦

Path Size
dist/assets/index-CgN1XV4b.js 161.99 KB (0%)
dist/assets/index-BsJUZYRr.css 6.13 KB (0%)

@mastermanas805 mastermanas805 merged commit db24d98 into main Jun 7, 2026
19 checks passed
@mastermanas805 mastermanas805 deleted the fix/live-ui-payment-drive-budget branch June 7, 2026 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants