The codebase, measured
Everything below is counted out of this repository's git history at the moment the running image was built. No number here was typed by hand, none of it is rounded in our favour, and a week of writing code without tests would show up on the second chart the day it happened.
115,514
lines of application code
954 files under app/src
161,384
lines of tests
678 PHPUnit classes, 51 Playwright specs
7,016
test cases
6,894 unit and functional, 122 browser flows
1.40×
test code per line of code
was 0.90× on day one
52 days, 983 commits on main, 46 of those days with a commit on them. That is about 2,172 lines of application code and 3,059 lines of test a day, every day, including the ones nobody worked.
Code, and the tests that hold it
The PHPUnit suite has been larger than the application it tests since the second week, and the gap has widened since.
- PHPUnit tests 155,097 lines
- Application code 115,514 lines
- Playwright suite 6,287 lines
- as at 9 Sep
Test code per line of application code
The one chart here that can go down. Shipping a feature with its tests barely moves it; shipping one without them bends it, and it does not recover on its own.
- Test lines per line of code 1.40×
- as at 9 Sep
Unit and functional tests
Counted as PHPUnit counts them, before data providers multiply them.
- Test methods 6,894
- Test classes 678
- as at 9 Sep
Browser flows
Playwright, driving a real browser against a real stack in CI on every pull request.
- Browser flows 122
- Spec files 51
- as at 9 Sep
Everything else
The templates a page is drawn from, the migrations the database is built by, and the prose explaining why any of it is shaped as it is.
- Twig templates 23,822 lines
- Documentation 23,896 lines
- Build & ops scripts 17,013 lines
- Migrations 7,656 lines
- Frontend assets 3,628 lines
- Configuration 2,663 lines
- as at 9 Sep
Where the 355,576 lines are
Today's tree, by the same buckets the charts use. Vendored dependencies are not counted, and neither are the four sibling repositories — the CLI, the tray app, the Terraform provider and the shared Go client are checked out here but released on their own cadence, and folding them in would make the curve mean nothing.
| Bucket | Files | Lines | Share | Since day one |
|---|---|---|---|---|
| PHPUnit tests | 717 | 155,097 | 43.6% | +152,767 |
| Application code (PHP) | 954 | 115,514 | 32.5% | +112,923 |
| Documentation | 111 | 23,896 | 6.7% | +23,517 |
| Twig templates | 302 | 23,822 | 6.7% | +23,627 |
| Build & ops scripts | 116 | 17,013 | 4.8% | +16,943 |
| Doctrine migrations | 127 | 7,656 | 2.2% | +7,186 |
| Playwright suite | 67 | 6,287 | 1.8% | +6,287 |
| Frontend assets | 34 | 3,628 | 1.0% | +3,515 |
| Configuration | 42 | 2,663 | 0.7% | +2,376 |
How this is counted
- One sample per day.
- Taken from the last commit on main that day, walking first-parent — the state a merge shipped, not the intermediate states inside somebody's branch. Days nobody committed on are absent rather than carried forward, so a flat segment is a real quiet fortnight and not an invented point.
- Lines are lines.
- Blank lines and comments included, because deciding which comments count is a judgement and this page is trying not to make any. Binary files and vendored dependencies are excluded; so are the four sibling repositories checked out alongside this one.
- Tests are counted the way the suite runs them.
- public function test* under tests/ and test( in a .spec.ts — the same three patterns App\Service\Testing\TestSuiteMetrics uses for the lozenges on the front page, so the two cannot drift. The executed count is higher: data providers multiply methods, and projections multiply flows.
- Coverage is a gate, not a measurement.
- There is no coverage report inside a running container, and there could not be one describing this exact build. What there is instead is a promise CI keeps on every push: the suite runs under coverage and the build fails below 100% of app/src. Lower that gate and the boast lowers with it, in the same commit.
Measured at build from commit 5a7cf9c8, . The whole series is available as /codebase.json.