Keep signup and checkout working as you ship.

Start with the tasks you cannot afford to break: a new user signs up, a customer pays, and the app grants access. Molar runs those checks in a real browser and saves the screenshot and pass or fail for each step.

Preview checkExample
Pull request01
Update checkout confirmation
pull/48 · 3 files changed
- status: pending+ status: confirmed+ receipt: attached
Preview browser02
preview.northstar.test
Three browser tests

Signup and verificationPassed

Invite a teammatePassed

Payment confirmationNeeds review

Result03
Trace attachedOne check needs review before merge.trace_48_checkoutExplore Trace

Describe the expected result

Write what the customer should see, run it in a browser, and keep the scenario file in your repository.

Use resettable service state

Point integration paths at supported Clones when live side effects make repeated CI difficult, then restore state before the next run.

Run it on every pull request

Add the scenario to Guard so it runs on pull requests, or on a schedule against your live site.

Start with signup and checkout

Pick one activation path and one revenue path. Check that email verification reaches the workspace and payment confirmation grants the expected access.

  • Signup and OTP
  • Checkout and receipt
  • Webhook-driven state changes
Payment and access stateIllustrative example
BrowserPro plan · $24Test card ending 4242Payment step
Clone statePayment acceptedpayment_intent.succeededCallback received
ApplicationOrder confirmedReceipt visible in test inbox

Start small

Start with one URL, one test account and one expected result. Run it on your machine or as a hosted run.

  • Authorized URL
  • Test identity
  • Expected result
Define the access for a runYour setup
Target

The app and environment to use.

Identity

The account and permissions for this task.

Task

The actions and result you authorize.

Add the failure branch next

Once the first test passes, add the branch that matters most: a declined payment, expired OTP, delayed callback, or missing receipt.

  • One happy path
  • One failure branch
  • A result for each run

Frequently asked questions

Have a specific workflow in mind?
Talk to us

Who uses Molar?

Molar is in a free beta, built for small teams that ship web apps without a QA team, and for developers whose coding agents need to test their changes.

Can a startup run Molar locally?

Yes. Runs against localhost use a browser on your own machine, and clones can run locally too.

How does startup access work?

Create a free workspace. Molar is free during the beta, with up to 25 hosted runs a day per organization. We can help you set up your first test on a call.

Start with one browser check.

Create a free workspace and describe the first flow to test. Or check a public page first, no account needed.

Free during the beta. No card.