Pricing Install

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.

110,394

lines of application code

903 files under app/src

155,166

lines of tests

650 PHPUnit classes, 51 Playwright specs

6,750

test cases

6,628 unit and functional, 122 browser flows

1.41×

test code per line of code

was 0.90× on day one

49 days, 911 commits on main, 43 of those days with a commit on them. That is about 2,200 lines of application code and 3,119 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 148,881 lines
  • Application code 110,394 lines
  • Playwright suite 6,285 lines
  • as at 6 Sep
A line chart of lines of code per day. Application code rises from 2,591 lines to 110,394; the PHPUnit suite from 2,330 to 148,881; the Playwright suite from 0 to 6,285. 0 50k 100k 150k 20 Jul 30 Jul 8 Aug 16 Aug 24 Aug 4 Sep 6 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.41×
  • as at 6 Sep
A line chart of the ratio of test code to application code per day, from 0.90× to 1.41×. 0.0× 0.5× 1.0× 1.5× 20 Jul 30 Jul 8 Aug 16 Aug 24 Aug 4 Sep 6 Sep

Unit and functional tests

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

  • Test methods 6,628
  • Test classes 650
  • as at 6 Sep
A line chart of PHPUnit test methods and classes per day, reaching 6,628 methods across 650 classes. 0 2k 4k 6k 8k 20 Jul 30 Jul 8 Aug 16 Aug 24 Aug 4 Sep 6 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 6 Sep
A line chart of Playwright flows and spec files per day, reaching 122 flows across 51 specs. 0 50 100 150 20 Jul 30 Jul 8 Aug 16 Aug 24 Aug 4 Sep 6 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,297 lines
  • Documentation 22,322 lines
  • Build & ops scripts 16,293 lines
  • Migrations 7,169 lines
  • Frontend assets 3,501 lines
  • Configuration 2,576 lines
  • as at 6 Sep
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 30 Jul 8 Aug 16 Aug 24 Aug 4 Sep 6 Sep

Where the 340,718 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 689 148,881 43.7% +146,551
Application code (PHP) 903 110,394 32.4% +107,803
Twig templates 295 23,297 6.8% +23,102
Documentation 110 22,322 6.6% +21,943
Build & ops scripts 110 16,293 4.8% +16,223
Doctrine migrations 120 7,169 2.1% +6,699
Playwright suite 67 6,285 1.8% +6,285
Frontend assets 33 3,501 1.0% +3,388
Configuration 42 2,576 0.8% +2,289

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