- status: pending + status: confirmed + receipt: attachedcommit 8e4c · 3 files changed
Know what a change did before it ships.
Connect a preview URL to important journeys. Molar checks the changed application in a browser and leaves evidence for review before merge.
preview.acme.testSignup and verificationPassed
Invite a teammatePassed
Payment confirmationFailed
Check the change
Run selected journeys against the environment created for a pull request.
See the failure
Open trace, screenshots, and status that explain where the preview diverged.
Gate with context
Use configured checks as part of review when repository support is set up.
A preview test in practice
A pull request changes checkout. The run opens the preview, buys a test plan, verifies the callback, and reports the order state.
- Preview URL
- Critical path scenarios
- Result attached to review
- status: pending + status: confirmed + receipt: attachedcommit 8e4c · 3 files changed
preview.acme.testSignup and verificationPassed
Invite a teammatePassed
Payment confirmationFailed
Start with a small suite
Choose the journeys where a regression matters most, then expand coverage as the team learns.
- Signup and login
- Checkout and payment
- Invites and webhooks
4242 4242 4242 424208 / 28 · Test cardPOST /webhooks/payment signature verifiedA few things
you might be wondering.
Have a specific workflow in mind?
Let’s talk it through
Does Molar test every pull request automatically?
Guard runs configured checks when repository connection and policy are set up.
Can previews use Clones?
Supported workflows can pair a preview with configured service clones.
What happens when a check fails?
The run records a failed or blocked outcome with available evidence.
Test a preview deployment.
Choose a concrete workflow. We’ll help you get the right setup for your application.