docs(testing): clarify integration vs acceptance policy#36
Open
GeorgesAlkhouri wants to merge 1 commit into
Open
docs(testing): clarify integration vs acceptance policy#36GeorgesAlkhouri wants to merge 1 commit into
GeorgesAlkhouri wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #36 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 23 23
Lines 1258 1258
=========================================
Hits 1258 1258
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
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.
Summary\n- add explicit integration vs acceptance/E2E scope definitions in AGENTS policy\n- make integration tests the default feature-coverage layer and keep acceptance as small top-level releasability smoke\n- require planning-time acceptance-test questions and explicit mapping into integration/acceptance plan items\n\n## Validation\n- make check-markdown-links