Demo run:312 checks·1 problem found

Protect every client store after launch.
Without building an in-house QA team.

nightly.run · 02:14 UTC
$ nightly run --checks=checkout,signup,payments
running…
0 passed0 failed6.2s total
#nightlyrun-alerts
02:16
revenue · P1

Checkout discount broken on iOS Safari, carts > $150.

Trace + screenshot attached. Suggested fix in thread.

verified by a human · 02:31

NightlyRun sits behind Shopify Partner agencies to protect every launch, migration, and retainer. We check each store's revenue-critical journeys overnight, then a human verifies every alert before your team or client sees it.

Start the seven-night pilot Book a 15-min call

One store. Three journeys. Seven nights. Staging only. No charge.

Prefer email? sanaev@nightlyrun.com
Every night

What we check, every night.

If it's where money or signups leave your site, we run it. Same flows, same devices, same browsers — every night.

Add to cart works
Discount codes apply
Checkout loads
iPhone checkout
Signup emails send
Pages load fast
02:14 — the catch

The bugs that cost you money look like this.

shop.brand.com/checkout
Cart · 2 items$187.00
COUPON10✗
Not a valid code
Pay $187.00
revenue · P1est. loss $2,400 / night
Free Range Eggs
1 dozen · $8
Total $187.00
Pay $187.00
50% OFF ENDS IN 04:12×
mobile · P1iOS Safari · 32% abandon
Signed up — check your inbox
POST /api/signup 200
HOOK /crm/lead 500
↳ retried 3× · dropped silently
silent · P2users never onboarded
inbox · you@company.com
  • Weekly digest08:04
  • Order #4192 shipped07:31
  • — reset your password —waiting 04:32
lockout · P2users can't return
08:00 — what you wake up to

Not a red dashboard. A verified alert and a weekly receipt.

#nightlyrun-alerts

Checkout discount broken on iOS Safari, carts over $150. Trace + screenshot attached. Suggested fix in the thread.

Verified by a human · 02:31

Weekly report · sample
  • runs: 312
  • failures caught: 2
  • est. revenue protected: $18,400

Sample report · illustrative until we have a week of your data.

How it works

How it actually works.

The technical part, for whoever on your team asks.

  1. Step 1

    Written in your language

    Playwright test suites written specifically for your store's flows — the exact paths a customer takes to give you money.

  2. Step 2

    Shipped into your own repo

    Committed as a pull request into your own repo. You own every line — if we part ways, nothing walks with us.

  3. Step 3

    Runs on every deploy + nightly

    GitHub Actions runs the suite on every deploy, plus nightly against production. Screenshot, video, and trace captured automatically on any failure.

  4. Step 4

    A human reviews every failure

    No noisy pager. A real person reproduces the failure before you're alerted, then you get Slack or email + a weekly report.

Selected work

~/projects
Open source

E-commerce Playwright Suite

Full Playwright + TypeScript suite covering login, search, cart, checkout, and mobile flows on a demo Shopify-style store. Page Object Model, fixtures, mobile viewports.

Reference repo

GitHub Actions CI Pipeline

Matrix runs across browsers, HTML report published, screenshot + video artifacts on failure, Slack webhook on red builds.

Deliverable

Sample QA Audit Report

Sample bug report from a demo store audit in the deliverable format: severity ranking, revenue impact estimates, reproduction steps, screenshots, recommended fixes.

Founder note

Built by a QA automation engineer.

I'm Muhammad, a QA automation engineer in the Bay Area. I build Playwright + TypeScript test suites, wire them into GitHub Actions and Jenkins, and I focus on the exact flows that lose stores money: cart, discounts, checkout, and signup.

NightlyRun is new. You'd be working directly with me, and every test I write lives in your repo, so you can check my work line by line. The open-source suites below are what my work looks like.

How we work together

Start free, then decide.

  1. 1.

    Free 7-night pilot.

    One store, three journeys, staging only. No charge.

  2. 2.

    You get the report.

    Every failure the suite caught, with traces, screenshots, and suggested fixes.

  3. 3.

    If it's useful, we set the price together.

    On a short call, based on how many stores and flows you need covered. Month-to-month.

Start the pilot Book a 15-min call
FAQ

Questions people ask before they book.

  • Do you write the tests in my repo, or somewhere else?+

    Your repo. Everything ships as a pull request against your codebase. You own every line of test code from day one — if you leave, nothing walks with me.

  • What happens when a test fails at 2am?+

    I investigate and hand you a reproduction + suggested fix within 2 hours. I don't hot-fix your production app — the fix is your team's call. You get a verified alert, not a noisy pager.

  • Which stacks do you cover?+

    Shopify (Liquid, Hydrogen, headless), Next.js, Remix, Rails, Django, custom SPAs. If it runs in a browser and you have a URL, I can test it. Native mobile is out of scope.

  • How long until I see the first test running?+

    Ten working days from kickoff to first nightly run against production. First failing test on your calendar, first Slack alert in your channel.

  • Do I need a staging environment?+

    Preferred but not required. Most flows can run against a production URL using seeded test accounts and payment sandboxes I set up as part of onboarding.

  • Can I cancel?+

    Yes. Every engagement is month-to-month, with no annual lock-in. If you cancel, you keep the entire test suite — it's in your repo.

Your next deploy shouldn't be a coin flip.

Start with one store, three journeys, and seven nights on staging. No charge.

Start the pilot Book a 15-min call