By platform

Test Shopify store before launch

You have products, a theme and a payment setup, but you have only seen the store while logged in as the owner. Mimiq sends simulated visitors through it in a fresh browser and shows where each one stops.

5 visitors try to .
First test free with an accountRun it from your coding agent

How do I test a Shopify store before launch?

Test it the way a buyer meets it: open the store in a private window while logged out, then walk from a product page to the payment step. Check the store password if the store is not open yet, that each product you sell is on the Online Store channel, and that a shipping rate exists for every country you ship to. A simulated test runs that same path with visitors who start logged out, and records each step where one of them stops.

What this looks like in a report

Who
Hiroshi, buying two ceramic mugs for his office
How they arrived
Opened the store from a link in a newsletter, on his phone
Where they stopped
Checkout, at the shipping step after typing his address

“I typed my address and the page says there are no shipping methods. Does this store ship to Japan at all? I will buy from a different mug shop.”

The fix. Add a shipping rate for Japan, or stop advertising that you sell there. Then type a Japanese address in a private window and confirm a rate appears before payment.

An illustration. Run a test to see your own.See a real sample report

Your admin login hides what a logged-out buyer sees

Shopify keeps the admin, where you edit products, apart from the storefront that buyers load. You check the store while logged in, so the admin shows you what you set up, not what a buyer gets. A product that is not on the Online Store channel, or a country missing from your shipping rates, can look fine in your admin. A buyer then lands on a missing product page, or reaches a shipping step with no option at all. Your admin shows no error for either, because from where you sit nothing is broken.

  • Open the store address in a private window while logged out, not in the tab where you edit products.
  • If a password page is on, enter the password as a visitor would, and confirm it opens the store.
  • Open each product you sell and check it is available on the Online Store channel.
  • Pick each option, such as size or color, and confirm the add-to-cart button responds to the choice.
  • At checkout, type an address in a country you sell to and confirm a shipping option appears.

How it works

  1. 01

    Open a private window and log out of the admin

    Load the store address the way a buyer would. Do not use the tab where you edit products, because your login changes what you see.

  2. 02

    Pick a product and every option

    Choose each size or color, add the item, and open the cart. Note any option that does nothing when you change it.

  3. 03

    Enter an address in each country you sell to

    Read the shipping options for each one. A country with no option is a country you cannot ship to, whatever your settings suggest.

  4. 04

    Stop at payment, then test payment separately

    Keep the run on the payment step. Test the payment in your provider's test mode with its published test card numbers.

The path one buyer takes, screen by screen

Test one buyer from the first screen to the payment step. The buyer lands on a product page, checks the price and looks for the option they want. They pick it, press add to cart, and the cart shows what they chose. Checkout comes next, and it asks for an address before it shows a shipping choice. A test of only the home page and the first product you built misses every screen after that. Each screen can fail on its own, and a buyer who hits the failure leaves without writing to you.

Where the owner's view hides the break

Your admin and the storefront are two different views, even in the same browser. The theme you chose can also lay out a product page differently on a phone than on a laptop. An option menu that opens fine on a laptop can sit behind a menu button on a phone that a visitor may never tap. Test both widths in a logged-out window. Mimiq visitors use laptop and phone browsers, so one run can show a phone visitor who could not reach the add button, with a screenshot of that step.

Shipping is the other half of the blind spot. You set rates for the countries you thought of, and a buyer from a country you did not list reaches the shipping step with nothing to choose. That step looks broken, but the store is doing what it was set up to do. Only an address from that country shows the gap, which is why a test needs one.

Test the payment step, not the payment

A checkout test goes up to the payment step and stops there, because visitors cannot pay with a real card. Test the payment itself in your payment provider's test mode, using its published test card numbers, and check that the order appears in your admin. An app that adds a step at checkout, such as a review widget or a loyalty box, belongs in the test too, because a buyer meets it before they pay.

Mimiq is independent and not affiliated with the platforms it names. Names belong to their owners.

What you get with Mimiq

  1. 01

    Run it by hand, or on every pull request

    Paste a link and a task in the app and watch the visitors work. Or run them on every preview deploy: the GitHub Action comments on the pull request, any other CI can call the MCP endpoint, and your coding agent can run it too.

  2. 02

    Bugs and usability problems in one report

    The browser records errors and failed or slow requests on the step they happened. The visitors say where the wording or the steps confused them, and where they left.

  3. 03

    Visitors that behave like your audience

    Each visitor is a different profile with a reason to be there, matched to who the page is for, described by you, or built from your own customers.

  4. 04

    A prompt to fix each problem

    Every problem comes with a fix to paste into Cursor, Claude Code, Lovable or any coding agent, and one prompt hands over the top problems at once. Then send the same visitors through again.

  5. 05

    Follow every visitor

    See each visitor's whole path, step by step with screenshots, and what it was thinking at every step. Ask any visitor a question.

The browser records relevant JavaScript errors and failed or slow app requests encountered during the run, attached to the step where they occurred. The visitors are simulated: they find problems, they do not predict how many real people will convert.

A theme update or a new sales channel can hide a product again

A store keeps changing after launch. A theme update, a new app at checkout, a shipping rate change or a product moved off the online channel can each break the path a buyer takes. Run the same logged-out visitors again after each change, before the next campaign sends traffic, and compare the step where they stopped with the last run.

Starter

Try it on one launch

$9 once
120 credits, never expire

About 4 tests of 5 visitors

  • Visitors on your landing page, signup and checkout
  • Where they left and why, with a fix to copy for each problem
  • Run it in the app or on every pull request
  • Ask any visitor a question, included
  • Test accounts and protected previews
Buy 120 credits

Builder

Test every build

$19 a month
500 credits every month

About 20 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Builder

Pro

Test every release, as a team

$49 a month
1,500 credits every month

About 60 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Cancel anytime
Choose Pro

Scale

Test at scale, every day

$149 a month
6,000 credits every month

About 240 tests of 5 visitors

  • Everything in Starter
  • Credits refill each month, and what is left rolls over once
  • Priority support
  • Cancel anytime
Choose Scale
$0for your first test, with a free account (Google sign-in, no card). It includes 50 credits, enough for 10 visitors. After that a visitor uses 5 credits, and packs start at $9 for 120 credits.
See a sample report

Questions

Will a test store show the same thing as the live store?

Only if you test the address buyers will use. A preview theme and the published theme can differ in content and settings, so test the live address, or the exact preview you plan to publish, from a logged-out window.

Does the test place an order?

No. Visitors go through the cart and checkout and stop at the payment step, because they cannot pay with a real card. Check the payment in your provider's test mode, then confirm the order shows in your admin.

Can this tell me how many buyers will purchase?

No. It does not predict how many real buyers will purchase. It shows where simulated visitors stop, with the step and a screenshot. Conversion numbers come from your analytics or from a live experiment.

What happens when the store is behind a password page?

With paid credits, you can give the simulated visitors the site password, so they get past the page. Without paid credits, they stop at the password page, and the report shows that step with a screenshot.

Keep reading

Send visitors and see what breaks first.

Your first test is free: sign in with Google and it starts right away. Last checked 2026-11-02.

5 visitors try to .