Testing Medusa: What to Test, What to Skip, and How
Commerce code moves money, so untested checkout logic is a liability. A pragmatic test strategy — what earns its keep, and what is theatre.
Eryx is a small studio of engineers and designers building production software for commerce, content, and ops teams.
Medusa.js storefronts, B2B portals, custom checkout, multi-region.
Next.js, React, TypeScript. SaaS dashboards, marketplaces, internal tools.
Agents, RAG, OpenAI/Anthropic integrations, custom workflow tools.
Sanity, Payload, custom dashboards. Where ops teams actually want to live.
Open-source Medusa modules, integrations, payment & shipping providers.
Tokens, components, Figma libraries. Stop rebuilding the same button.
1 week — scope, audit, plan
2 wk — wireframes → hi-fi
4–8 wk — sprints, weekly demos
ongoing — measure, improve
Usually within two weeks. Discovery can often start sooner — it is one week of scoping and does not need the full team.
You do, from the first commit. We work in your repository, on your infrastructure, with your accounts.
Often. The Embed engagement exists for exactly that — a senior squad in your standups, your tools, your roadmap.
Thirty days of on-call is bundled into every build. After that it is a retainer or a clean handover, your call.
Eryx ships like a senior in-house team. Transparent code, weekly demos, no surprises — we doubled our time-to-market on the rebuild.
Commerce code moves money, so untested checkout logic is a liability. A pragmatic test strategy — what earns its keep, and what is theatre.
Self-hosting means owning the question 'is checkout working?'. Structured logging, tracing, the four metrics that matter and alerts that do not cry wolf.
Four cache layers, one rule about carts, and the invalidation strategy that stops a price change taking twelve hours to appear.