docs(testing): add feature-surface test coverage map (PP-b1n) - #2325
Merged
Merged
Conversation
Add docs/testing/coverage-map.md — the inverse of the spec audits: for each user-facing feature surface, which of the four test layers (unit, integration, smoke, full E2E) cover it, with representative files cited to make each cell checkable. Reference it from the pinpoint-testing skill in two places (the "Where Existing Coverage Lives" section and "Elsewhere") so future agents discover it. The map is hand-maintained and grounded in the test files present at authoring time; a ✓ is a presence signal, not a completeness score. A "Known gaps" section flags blank cells that may be real gaps (What's New / changelog, the member-facing help/FAQ pages) rather than by-design cheaper-layer choices. Satisfies the PP-f86 acceptance-criterion #6 follow-up (PP-b1n). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011JjbshZ69xRTZNUWeVgZZA
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
timothyfroehlich
added
the
ownerless
Claude
timothyfroehlich
removed
the
ownerless
Owner
Author
Claude Code review (medium)Reviewed head —Claude |
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds
docs/testing/coverage-map.md— the inverse of the existing specaudits. For each user-facing feature surface, it shows which of the four test
layers (unit, integration, smoke, full E2E) cover it, with representative test
files cited so each cell is checkable. Grouped logically (Auth, Issues,
Machines, Timeline, Collections, PinballMap, Notifications, Admin, Profiles,
Settings, Public routes, Dashboard/shell, MCP/API, Permissions, Shared UI,
Tooling).
Also references the new doc from the
pinpoint-testingskill in two places(the "Where Existing Coverage Lives" table intro and "Elsewhere") so future
agents discover it.
Why
Satisfies the PP-f86 acceptance-criterion #6 follow-up tracked by PP-b1n.
The spec audits answer "does this spec violate a principle?"; this map answers
the other direction — "for feature X, where is it tested?" — so coverage gaps
become visible at a glance.
Notes for the reviewer
surface), not a completeness or quality score. Blank = "look before assuming
covered."
test files present at authoring time. The maintenance note asks contributors
to tick/add the row in the same PR when they add a surface or a layer.
gaps rather than by-design cheaper-layer choices (e.g. What's New / changelog
has no test at any layer; the member-facing
help/*MDX pages and FAQaccordion are untested).
sandbox — see PP-rhzk — so unit/integration/E2E are left to CI). The map was
reviewed by three subagents (correctness, bead-acceptance, maintainability);
their findings — a false Full-E2E ✓ on the machine-linking row, two missing
surfaces, and the generation-model wording — are folded in.
ownerless
Opened by the unattended nightly bead routine; labeled
ownerlessbecause nosession is driving its lifecycle (CI, review threads, merge-readiness). An
orchestrator or Tim can adopt it.
🤖 Generated with Claude Code
https://claude.ai/code/session_011JjbshZ69xRTZNUWeVgZZA
Generated by Claude Code