test: refine test layer planning skill guidance#389
Open
summergan wants to merge 3 commits into
Open
Conversation
Keep Test Pyramid as the familiar cost model, move MECE surface/layer/quality/size decisions into Test Planner, and add eval coverage for API, contract, and frontend integration boundaries.
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
1 participant
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.
Refine the testing guidance so agents choose test layers by project surface and changed behavior, rather than treating all integration-style tests as one bucket.
Changes include:
test-driven-developmenttesting-patterns.mdwith examples for frontend integration, API, contract, backend integration, E2E, fixtures, and flaky test triagetest-engineeroutput format to require explicit layer decisions