Multi-Context & Inbox-Driven Testing
Test collaboration flows across multiple users and handle 2FA or email links natively in a single test run without mocking.
Start for free • No credit card required
Multi-user scenarios
Simulate one user taking action while another verifies the result in a separate browser session.
Context switching
Move between isolated sessions without losing state in the original test flow.
Inbox-driven flows
Read emails, extract codes, and open links without bolting on custom inbox plumbing.
Modern applications are collaborative. Chat apps, admin approvals, and multiplayer editors require testing how multiple users interact in real time. Mechasm supports multi-context execution so those flows can run inside a single test definition.
How teams use multi-context testing
The platform is designed for workflows that are awkward to express as separate disconnected test scripts.
Real-time collaboration
Verify that actions from one user become visible for another user in the same run.
Role-based approvals
Switch between standard-user and admin sessions to validate request and approval flows.
Email-assisted onboarding
Continue invite, reset, and verification journeys using links or codes delivered during the test.
Why it matters in practice
Multi-context execution improves realism while keeping the run inspectable and deterministic.
Session isolation
Each context keeps its own cookies, local storage, session storage, and cache so users stay isolated.
Flexible email link handling
Open a reset or invite link in the current page, a new tab, or a separate isolated context depending on the workflow.
Per-context debugging assets
Videos and trace views stay separated by session so it is easier to understand what happened for each user.
Explore the rest of the platform
Dive deeper into the product surface around this capability and see how it connects to the rest of Mechasm's autonomous testing workflow.