Test the path your users actually take.

A web app can look healthy while a callback, redirect, verification code, or receipt path is broken. Molar combines browser exploration, goal based execution, and integration fixtures to put those transitions inside the test conversation.

Get started Read the docs

Application mapIllustrative flow

Your application

Guest

Homepage

Browse plans

Create account

Member

Workspace

Invite teammate

Observed pathNext branch

PagesActionsOutcomesEvidence

Start with a URL

Use a live or local authorized URL and a concrete claim such as a visible receipt or completed onboarding step.

Observe before acting

Read bounded accessibility observations and structured page context before asking the agent to change state.

Keep the result

A run can retain screenshots, trace identifiers, and artifact references for review and later diagnosis.

Coverage with a reason

Focus on journeys where the browser, backend, and third party must agree. That is where a screenshot alone cannot establish correctness.

Browser assertions
Auth and verification loops
Payment and webhook transitions

Go to documentation

Preview checkIllustrative workflow

Update checkout confirmationPull request #48

- status: pending
+ status: confirmed
+ receipt: attached

commit 8e4c · 3 files changed

deploy

Preview environmentpreview.acme.test

Signup and verificationPassed

Invite a teammatePassed

Payment confirmationFailed

3 journeys checked Trace attached to the failed check

Choose local or hosted execution

The unified CLI supports local browser verification and hosted fallback. Hosted runs use scoped credentials and target authorization, with private beta limits applying.

Talk through your use case

Live evidenceIllustrative workflow

checkout.acme.test / confirmation

Order confirmedReceipt sent to test inboxpayment_intent.succeeded

Run trace 00:08—00:10

Open checkoutScreenshot captured200

Confirm paymentPOST /webhooks/payment200

Receive receiptTest inbox matchedready

Network and console evidence attached

A few things
you might be wondering.

Have a specific workflow in mind?
Let’s talk it through

Can I assert a business outcome?

Yes. The verify command accepts a natural language assertion, such as an order confirmation number being shown, against a URL or prior task.

Does Molar replace Playwright?

Molar can export or produce Playwright oriented artifacts in supported workflows, while Playwright remains a useful direct test tool.

Can I test a logged in path?

Use an authorized saved profile or login credential reference. The system keeps login state origin bound and scopes access.

Verify a web journey.

Choose a concrete workflow. We’ll help you get the right setup for your application.

Get started Talk to the team