fix: flaky payment-details test with Stripe iframe waits #1584
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.

Issue: #1531
Test:
https://github.com/antiwork/flexile/actions/runs/20915820205/job/60089005090#step:12:270
Problem
The test was timing out because:
elements-inner-payment) loads asynchronously from an external CDNSolution
Added implicit waits before each Stripe iframe interaction:
await expect(stripePaymentFrame.getByLabel("Test Institution")).toBeVisible();before clicking "Test Institution" in both the initial "Link your bank account" flow and the "Edit" flowThis follows the same pattern used in the microdeposits test in the same file (waiting for "Routing number" before interacting with the bank frame).
Screenshot
couldn't able to test this locally because I don't have a Stripe account currently.
So, I am relying on CI checks for this test verification.
AI Disclosure
I have used Claude Opus 4.5 to implement the fix.