Code, tests & documentation

Chenile by the numbers

How much code, tests and documentation make up the 11 Chenile repositories — measured from the source, not estimated.

Measured October 3, 2026 from the working copies of the 11 repositories, including the in-progress 2.1.31 work.

33135
Lines of production Java
790 source files
20840
Lines of test Java
63 test lines per 100 production lines
74
Maven modules
across 11 repositories, one release train
79783
Words of documentation
site articles + repository guides

Code, repository by repository

Lines are non-blank, non-comment Java lines; Javadoc is counted separately. Tests are everything under src/test. Front-end lines cover the React consoles (Admin UI, process dashboard, PlantUML viewer).

RepositoryModulesJava filesProduction linesTest linesJavadoc linesGherkin featuresFront-end linesCommits
chenile-parent1000000102
chenile-core12478127936977268641693152
chenile-query-workflow-blueprints132115936378475191379125
chenile-process-management1116236122788288653360
chenile-service-registry4311130721422051
chenile-proxies2346585281040047
chenile-security1177286219071320055
chenile-messaging8110259021874490065
chenile-bdd3115610880043
chenile-others571202013261651041
cconfig4359736221602047
All 11 repositories74122033135208404865243605788

Alongside the Java there are 356 configuration and schema files (XML, JSON, YAML, properties, SQL — state machines, query metadata, process definitions, migrations) and 2071 lines of Gherkin across 24 feature files.

Where the weight sits
chenile-core — the exchange, the interception pipeline, HTTP binding, the state machine and workflow runtime, Owiz, MCP and the Admin UI — holds roughly two-fifths of the production code. The application blueprints (chenile-query-workflow-blueprints, chenile-process-management) are next; the integration repositories (security, messaging, registry, proxies) are deliberately small, because they plug into the same pipeline rather than re-implementing it. chenile-parent is a build baseline with no Java.

Tooling outside the release train

chenile-gen (JGen) adds 2385 production and 359 test Java lines in 17 Maven modules, plus 388 Mustache templates that make up its 12 built-in blueprints — see the blueprint reference.

Documentation

SourcePages / filesWords
chenile.org — Concept articles158963
chenile.org — Developer guides2113774
chenile.org — Release notes33315
chenile.org — Video episode pages124094
chenile.org — Other site pages52176
Repository guides & READMEs (Markdown in the 11 repos)6147461
Total written documentation11779783

On top of the prose:

  • 4865 lines of Javadoc in the source, published as API reference.
  • 791 automated framework tests (plus 22 in JGen) passing for the 2.1.31 release, with zero failures — see the release process.
  • 24 executable Gherkin specifications — documentation that is also a test (see BDD).
  • The video series — 12 narrated episodes, about 21 minutes in total, with captions and full scripts on each episode page.
  • Interactive explainers on the concept pages, and generated workflow diagrams from every state machine.

How these numbers are produced

The figures come from scripts/codebase-stats.py in this site’s repository, which walks the 11 repository checkouts and writes _data/codebase.yml; this page renders that file. Build output (target, dist, node_modules), shared site styling and IDE folders are ignored. To refresh after a release:

cd cheniledocs.github.io
python3 scripts/codebase-stats.py ..     # path to the folder holding the 11 repos