Checkout with Adyen in automated tests
Adyen is one of the most common payment providers for modern ecommerce, and it is also one of the most painful to automate with a traditional framework. The checkout UI is split across multiple secure iframes, which often turns a simple payment step into a long sequence of brittle selectors and repetitive steps.
The Checkout with Adyen step is designed to remove that friction. It lets you complete Adyen payments quickly and reliably inside DoesQA, without bloating your flow with iframe handling or low-level workarounds.
Adyen checkout is one of the highest value areas to automate because it sits directly on the revenue path. When it breaks, teams feel it immediately. This step helps you keep coverage high in the places that matter most, without turning payment tests into a maintenance burden.
Why this step saves so much time
Payment automation fails for predictable reasons:
Each field (card number, expiry, CVC) is hosted in a different iframe
Selectors change more often than the rest of checkout
Teams end up duplicating large chunks of steps across flows
Flakiness increases because the test has to coordinate several embedded contexts
This step collapses all of that into one clean action.
What you can test with Adyen checkout
You can use this step whenever your flow reaches an Adyen widget, including:
Card payments (credit and debit)
Adyen-supported PayPal flows
Standard purchases, subscriptions, and one-off payments
Checkout journeys that include address selection, delivery options, discount codes, and basket changes
It is especially useful when paired with branching flows, because you can keep one main checkout journey and branch for payment method variations without duplicating the entire checkout setup.
Two checkout modes for different goals
This step supports two common modes so you can choose the right level of completion for the test you are building:
Fill details
Useful when you want to validate that the widget loads, accepts inputs, and is ready to submit.
Fill details and checkout
Useful when you want to validate the full purchase path and confirm the order completes successfully.
Faster setup with default test card data
To keep test creation fast, the Adyen step includes sensible default test card details so you can get a payment flow running quickly. You can keep these defaults for early coverage, then later swap in your own card values or data strategies as your pack matures.
Building reliable payment coverage without step bloat
A good approach is:
Use DoesQA to automate the whole checkout journey up to payment
Use the Adyen step to complete payment cleanly
Assert the post-payment result (order confirmation, success state, receipt page)
This keeps payment automation readable, consistent, and easy to maintain, even as your application evolves.