Molar.
Get started

Check sign-in from signup to workspace.

Give Molar a goal such as “create an account, enter the email code, and open the workspace.” It follows the forms and redirects, then reports where access was granted or the setup stopped.

Get started free Read the docs
Signup and email verificationExample
Browser01
northstar.test / sign up
Create accountTest sign-in
Test inbox02
Verification codeInbox message matched
482190
Application session03
Workspace readyMember identity verifiedsession_7f24
Verified emailOnly a verified identity opens the workspace.

Follow real browser steps

Run forms, redirects, codes, and protected pages in the order a customer uses them.

Create test identities

Use separate identities for each role so permissions and invitations are checked against the right account.

Name the failure path

Check expired codes, denied access, sign-out, and invitation cases with a result you can inspect.

Signup, verify, continue

Run “create an account, enter the email code, and open the workspace.” The returned status identifies the page or access step where the journey stopped.

  • Signup and email verification
  • OAuth redirects
  • Invites and workspace roles
From signup to workspaceIllustrative example
Example pathsignup / verify / workspace observed
01Signupform submitted
02Email codemessage matched
03Workspaceassertion passed
Browser assertionworkspace heading is visibleScreenshot · trace event · step 02

Sessions need checks too

Check refresh, reload, sign-out, and access to a route that should remain protected after the first login.

  • Session persistence
  • Expired credentials
  • Protected routes
Role and permission matrixIllustrative example
Workspace accessexample.acme.test site-specific account
RoleProjectsBillingMembers
Owner edit manage invite
Member edit— none— view
Invitee— pending— none— none
Expired code: access remains blocked

Frequently asked questions

Have a specific workflow in mind?
Talk to us

Can I test sign-in with Google or GitHub?

It works when the provider’s sign-in host is in your project’s allowed hosts, but many providers block automated sign-in. Test your app’s own email sign-in where you can.

How are OTP messages handled?

Supported email and SMS clones provide controlled messages and codes.

Can I keep existing auth tests?

Yes. Keep your Playwright tests; Molar checks run alongside them.

Verify an auth journey.

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

Get started free Check a public page

Free during the beta. No card.