Skip to content

docs: state measured test-dir count and depth per codebase#1

Merged
stephendchu merged 2 commits into
mainfrom
docs/test-infra-depth
Jun 13, 2026
Merged

docs: state measured test-dir count and depth per codebase#1
stephendchu merged 2 commits into
mainfrom
docs/test-infra-depth

Conversation

@stephendchu

Copy link
Copy Markdown
Owner

Makes the discoverability variable (the study's independent variable) concrete.

Changes

  • README "Three codebases" table — adds measured test dirs under root and max test-file depth columns (pydantic 18 / depth 1; dbt-core 105 †; SQLAlchemy 34 / depth 2).
  • README "The gradient" — adds a sentence clarifying the three repos load discoverability on different axes: pydantic shallow+narrow, dbt-core broad, SQLAlchemy deep+gated (zero test files at root, behind the custom sqlalchemy.testing plugin).
  • docs/repos.md — new "Test-infrastructure depth" section with full depth distribution, per-repo reading, and the measurement command.

Honest caveat

dbt-core's 105-dir figure is footnoted as study-era only: main is now a Rust rewrite (no Python tests/), config.py clones HEAD without pinning a SHA, and data/commits/dbt-core/ is gitignored — so it isn't re-measurable. Disclosed as a reproducibility gap; SHA-pinning is the fix.

pydantic and SQLAlchemy measured at current HEAD via --depth 1 clones.

🤖 Generated with Claude Code

Make the discoverability variable concrete: add measured "test dirs
under root" and "max test-file depth" to the README codebases table and
a full depth-distribution breakdown in docs/repos.md (pydantic 18 dirs /
depth 1; SQLAlchemy 34 / depth 2 with zero files at root). Clarify the
gradient loads on different axes (breadth vs depth vs custom framework).

dbt-core's 105-dir figure is footnoted as study-era only: main is now a
Rust rewrite and config.py clones HEAD without pinning a SHA, so it is
not re-measurable. Disclosed as a reproducibility gap.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@stephendchu stephendchu force-pushed the docs/test-infra-depth branch 2 times, most recently from b1c5bbb to 311586c Compare June 13, 2026 22:39
Add the end-to-end pipeline flowchart (commit -> deleted worktree ->
A1/A2 arms -> judge/metrics -> result) to the README, and wire Mermaid.js
into the custom Jekyll layout so ```mermaid blocks actually render on the
GitHub Pages site (kramdown emits language-mermaid code blocks that
Mermaid does not pick up on its own).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@stephendchu stephendchu merged commit 75a5ed3 into main Jun 13, 2026
1 check passed
@stephendchu stephendchu deleted the docs/test-infra-depth branch June 13, 2026 22:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant