What we've learned building and running regression testing for headless commerce: baselines, firewalls, test data, and the diffs that matter.
Linear QA assumes you know the expected result. For CMS-driven systems you don't. Here is the two-phase, before-and-after approach I used to test the untestable.
API testing in CI/CD that catches breaking changes: wire regression checks into GitHub Actions or any pipeline and fail the build on critical changes.
How to test APIs behind a firewall from a SaaS platform: remote executors use outbound-only HTTPS, so there are no inbound rules, open ports or VPNs.
API regression testing beyond contract tests: how content regression testing catches the silent data changes that break storefronts and apps.
Most e-commerce test failures are test data failures. How to manage payment test cards, customers with real inboxes, international addresses and OTP.
GraphQL has one endpoint and infinite responses, which makes regression testing tricky. A guide to snapshot-based regression testing for GraphQL.
