grey.ooo
someones.computer
Pricing Install
Sign in

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.

152,886

lines of application code

1,329 files under app/src

212,309

lines of tests

931 PHPUnit classes, 56 Playwright specs

9,273

test cases

9,143 unit and functional, 130 browser flows

1.39×

test code per line of code

was 0.90× on day one

104 days, 1,617 commits on main, 95 of those days with a commit on them. That is about 1,445 lines of application code and 2,019 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 205,296 lines
  • Application code 152,886 lines
  • Playwright suite 7,013 lines
  • as at 31 Oct
A line chart of lines of code per day. Application code rises from 2,591 lines to 152,886; the PHPUnit suite from 2,330 to 205,296; the Playwright suite from 0 to 7,013. 0 100k 200k 300k 20 Jul 8 Aug 24 Aug 13 Sep 29 Sep 15 Oct 31 Oct

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.39×
  • as at 31 Oct
A line chart of the ratio of test code to application code per day, from 0.90× to 1.39×. 0.0× 0.5× 1.0× 1.5× 20 Jul 8 Aug 24 Aug 13 Sep 29 Sep 15 Oct 31 Oct

Unit and functional tests

Counted as PHPUnit counts them, before data providers multiply them.

  • Test methods 9,143
  • Test classes 931
  • as at 31 Oct
A line chart of PHPUnit test methods and classes per day, reaching 9,143 methods across 931 classes. 0 2.5k 5k 7.5k 10k 20 Jul 8 Aug 24 Aug 13 Sep 29 Sep 15 Oct 31 Oct

Browser flows

Playwright, driving a real browser against a real stack in CI on every pull request.

  • Browser flows 130
  • Spec files 56
  • as at 31 Oct
A line chart of Playwright flows and spec files per day, reaching 130 flows across 56 specs. 0 50 100 150 20 Jul 8 Aug 24 Aug 13 Sep 29 Sep 15 Oct 31 Oct

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 27,052 lines
  • Documentation 29,611 lines
  • Build & ops scripts 21,371 lines
  • Migrations 9,819 lines
  • Frontend assets 3,748 lines
  • Configuration 3,562 lines
  • as at 31 Oct
A line chart of the remaining parts of the repository per day: templates, documentation, scripts, migrations, frontend assets and configuration. 0 10k 20k 30k 20 Jul 8 Aug 24 Aug 13 Sep 29 Sep 15 Oct 31 Oct

Where the 460,358 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 985 205,296 44.6% +202,966
Application code (PHP) 1,329 152,886 33.2% +150,295
Documentation 94 29,611 6.4% +29,232
Twig templates 339 27,052 5.9% +26,857
Build & ops scripts 176 21,371 4.6% +21,301
Doctrine migrations 172 9,819 2.1% +9,349
Playwright suite 73 7,013 1.5% +7,013
Frontend assets 36 3,748 0.8% +3,635
Configuration 43 3,562 0.8% +3,275

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 f90c63cd, . The whole series is available as /codebase.json.