A browser suite that had never passed (0 of 103) was repaired to 111 passing tests, and a unit and integration layer that did not exist was added: 458 tests. 569 tests in all, 530 of them added.
An industrial manufacturer's web application, where the existing browser tests had never passed and there were no unit or integration tests.
Merge the pull requests
Every test, one square each
0 of 103 browser tests passing, and 0 unit or integration tests
Browser suite repaired to 111 passing, and 458 unit and integration tests added: 569 in all, 530 of them new
- Browser 111
- Client 207
- Server 251
Each square is one test, drawn the same size in both grids. Squares are grouped by layer and coloured by it; they do not stand for individual named tests.
| Value | Method | Recorded | Scope |
|---|---|---|---|
| 0 of 103 to 111 browser tests passing | Playwright run at the start of the engagement, and counted again with all four pull requests merged | 2026-09-24 | The client's browser (end-to-end) suite |
| 0 to 458 unit and integration tests | Counted with all four pull requests merged: 207 client tests on Vitest and 251 server tests on Jest, where none existed before. 129 of them are unit tests behind job, part and subtask validation, which a browser suite would need a test per route to cover | 2026-09-24 | The new unit and integration layer |
| 569 total, 530 added | Counted with all four pull requests merged: 111 browser, 207 client, 251 server | 2026-09-24 | Every test in the application, both layers |
Dates are when each figure was recorded for this site; the work itself is dated in the setting above.
What this does not prove
The browser figure is a repair of a suite that already existed and never passed; the 458 unit and integration tests are new work, covering code paths the browser tests miss or reach differently. The totals count every test across all four merged pull requests, not the running state at any single moment.