Example threads. These questions and answers were written by the SDODS team to document real problems and how to fix them. The people named are illustrative, not real users. Questions asked on this site are marked new.
Checkout uses Elements, so the card number is inside an iframe. The obvious step does not find it:
When I fill the "Card number" field with "4242424242424242"Could not locate "Card number" fieldWhich is fair enough — it is not in the main frame. I cannot find a frame step in the step library. Is there one under a name I would not guess?
Accepted answer
There is no iframe step. Every UI step in the shared library resolves against the scenario's main frame, so from a feature file alone the Elements fields are unreachable. There is an open issue proposing a set of frame and tab steps; none of it exists yet.
What does exist is the hook on the page object base class — frame(name) — so this is a page object away rather than blocked:
@When('I enter the test card')
async enterTestCard() {
const card = this.frame('__privateStripeFrame');
await card.getByPlaceholder('1234 1234 1234 1234').fill('4242424242424242');
}Expose one project step per meaningful action rather than a generic "switch to iframe" step — I enter the test card reads better in the feature than three frame-switching lines, and when the shared steps do arrive you replace the body and leave the feature files alone.
See page objects for how the method binds to the step.
One thing that surprised us: on Elements the number, expiry and CVC are separate iframes, so if you were hoping for one switch to the payment iframe and then three fills, that is not the shape of it. A single method that fills all three is much less annoying than three steps, and it is also the only place you have to change when the provider reorganises its frames.
Wrap commands and output in triple backticks and they will render as a code block.
Checking whether you’re signed in…
Have a different question? Ask it.