Summary
The documented test counts disagree across the repository. README reports 367 tests, docs/architecture.md reports 295 tests, and a source scan currently finds 388 TEST_CASE/pytest-style test markers.
References
README.md: test suite section reports 367 testsdocs/architecture.md: test suite section reports 295 teststests/ and mcp/tests/: current source markers indicate a different count
Impact
Stale counts make release notes and contribution guidance look unreliable. They also make it harder for contributors to know whether they are running the expected suite.
Suggested Fix
Either regenerate the counts and normalize all docs, or avoid exact totals in long-lived prose and point users to ctest -N, labels, and CI output for authoritative numbers.
Summary
The documented test counts disagree across the repository. README reports 367 tests,
docs/architecture.mdreports 295 tests, and a source scan currently finds 388TEST_CASE/pytest-style test markers.References
README.md: test suite section reports 367 testsdocs/architecture.md: test suite section reports 295 teststests/andmcp/tests/: current source markers indicate a different countImpact
Stale counts make release notes and contribution guidance look unreliable. They also make it harder for contributors to know whether they are running the expected suite.
Suggested Fix
Either regenerate the counts and normalize all docs, or avoid exact totals in long-lived prose and point users to
ctest -N, labels, and CI output for authoritative numbers.