ComposalWhere the time goes today
Tests log in as one user
A single test account cannot catch what happens when two people work on the same thing at once.
Permissions are checked by hand, or not at all
Who can see and change what is checked rarely, and almost never as the person you are worried about.
Test accounts are clean, production is not
Real users have years of history, odd data, and feature flags. A fresh account hides the bugs that live there.
Give each agent a role
Personas have their own sign-in, goals and permissions: admin, collaborator, visitor. Add as many as your product has.
Let them act on the same product
In one journey, one persona acts and another has to see the result. Composal checks each side, in order, with each agent’s evidence.
Use accounts that look like production
Persistent accounts with realistic data, feature flags and edge cases, so what the agents find is what your users would.
Bugs between users
The sharing, notification and permission bugs a single test account cannot see.
Permissions that hold
Every persona is checked for what it can and cannot do.
Production-shaped findings
Realistic accounts mean realistic bugs, not test-data noise.