Lab, internal tooling
The QA chassis
A reusable end-to-end testing rig: one command runs browser journeys on phone and desktop and files the evidence.
- Services
- App or CRM
- Stack
- Playwright, axe, An isolated local stack
- Updated
Context
Every app we launch gets checked in real browsers first. The QA chassis is the rig that makes that repeatable, instead of an afternoon of clicking around and hoping.
It is internal tooling, and it earned its keep on the Le Palais build.
Problem
Clicking through an app by hand stops working once it has more than a few screens. With several roles and a payment flow, nobody can walk every path before each release.
Tests that share a database also leak into each other. A journey needs a clean, known starting point every time it runs.
Approach
One command does the setup: it resets an isolated local stack, mints a signed-in session for each role, and runs Playwright journeys across phone and desktop projects.
The same run checks accessibility with axe, triages what failed, and writes one evidence folder per run, so every result has somewhere to point.
Outcome
On the Le Palais build it ran the staff journeys at phone and desktop sizes, and each run left its evidence folder behind.
The rig is generic on purpose, so the next app starts with its testing already in place.
- From a clean stack to an evidence folder
- One command
Stack
- Playwrightthe browser journeys, phone and desktop
- axeaccessibility checks on every run
- An isolated local stackreset before each run
Tell us what you are working on.
A few lines about your business is enough to start. We reply with questions and a plain next step.