ShopNex GitHub ★ 373

Testing

What we test

Not only tests we run: results you can read. Every change to main runs the checkout, payment and admin flows below in a real browser, against a freshly installed shop.

All tests passing

Latest run on main, November 20, 2026 at 3:49 PM UTC. 29 of 29 browser tests passed. 317 of 318 API tests passed.

Open the full report See the CI run

Browser flows

What a shopper and a merchant do

  • Abandoned cart emails 3 of 3 passing
  • Admin sign-in and first run 2 of 2 passing
  • Checkout payments 5 of 5 passing
  • Shopper checkout 1 of 1 passing
  • cookie-consent.spec.ts 6 of 6 passing
  • customer-privacy.spec.ts 3 of 3 passing
  • invoice.spec.ts 5 of 5 passing
  • product-custom-fields.spec.ts 1 of 1 passing
  • Carrier shipping rates 1 of 1 passing
  • staff-access.spec.ts 2 of 2 passing

How we test

So the results mean something

  • A fresh shop every run

    The app is built, migrated and seeded on an empty database, then tested through the browser and the API, the way a new install behaves.

  • No retries

    A test that fails once is reported as failed. Flaky tests are fixed or quarantined within days, not hidden.

  • Upgrades are tested

    Every night the latest release is installed, filled with data, upgraded to the current build, and compared. Lost or changed data fails the run.

  • Evidence on failure

    A failed test keeps a trace, a screenshot and a video in the report, so the cause can be read, not guessed.

Not yet

What is not covered

Checkout against Stripe test mode with real webhooks, failure scenarios (two buyers for the last item, refunds, rounding, staff permissions in the UI), and a nightly run with a longer history are still planned. They are on the roadmap, and the full plan is in the e2e plan.