Member-only story
Playwright E2E Testing Across Client and Admin Portals
How to test one business workflow across separate users, sessions, applications, and backend state without turning your Playwright suite into a flaky mess.
Your client portal test passes.
Your admin portal test passes.
Production still breaks.
Why?
Because the real business workflow does not stop at the boundary of either application.
A customer submits a request in the client portal. An administrator reviews it somewhere else. The backend changes state. Then the customer returns and expects to see that change.
Testing those applications independently can miss the most important failure:
the handoff between them.
This is where Playwright becomes especially useful. Its browser contexts can run completely isolated sessions inside one test, which makes scenarios involving different authenticated roles practical without launching separate test processes.
Let’s build the kind of E2E workflow I would actually want in a production project.
