commercetools test automation

Commerce & search

A headless storefront can change without the commerce project changing, and the other way around. DoesQA proves the shopper journey still works after either change.

commercetools

Test commercetools storefronts and headless checkout journeys, without code.

What we test on commercetools

  • Storefront browse, search and product pages

  • Cart, checkout and payment

  • Customer accounts

  • Locales, currencies and channels

  • Orders through the API or back office

How to test commercetools

Test the rendered storefront, not only Merchant Center. Use a staging or other non-production commercetools project, so tests do not depend on live catalogue changes.

Walk a product you control from listing to checkout, pay with the payment provider’s published test details, and confirm the order through the storefront or the API. Re-run after a storefront release, and after a catalogue or project change.

In DoesQA, you build that shopper journey as a Flow and run it from CI in a hosted real browser. API steps can read the project with GET and Check JSON Value in the same Flow. If card fields sit in an iframe, use Switch Frame, Set value and Switch to parent frame.

commercetools test checklist

  • A known product appears in search or listing pages and opens correctly.

  • Add it to the cart and complete checkout with test payment details.

  • A signed-in account journey completes, if you offer accounts.

  • Re-run the same journey on a second locale, currency or channel if you sell in more than one.

  • An API or back-office check confirms the order landed.

Where commercetools tests usually break

The storefront and the project can change separately.

A suite that only runs on a storefront deploy will miss a catalogue change, and the other way around. Run after both.

Live projects change under you.

Point the test at a staging or non-production project, and use products you control.

Locales and channels hide failures.

A journey that passes in one market can fail in the next. In DoesQA, drive locale, currency and channel with Values.

What you need to get started

  • A staging or non-production storefront URL, plus a commercetools project you can test against, and at least one product you control. commercetools documents projects, APIs and staging versus production environments in its official docs: commercetools documentation and API general concepts (fetched 10 November 2026).

  • Test payment details from the provider on that storefront, not live cards. For 3D Secure, see that page.

Trusted by teams that ship every day

Our customers test commercetools with DoesQA on every release.

DoesQA Flows dashboard

Get your next release tested end to end.

Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.

DoesQA Flows dashboard

Get your next release tested end to end.

Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.

Get your next release tested end to end.

Hosted journeys with email, MFA, and branching. Shared Elements keep maintenance low. Pass and fail from real hosted browsers.