Docs: enforce testing strategy validation - #1025
Merged
Merged
Conversation
|
@gracepeterfejokwu Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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.
Closes #933
Goal
Add automated enforcement for the repository’s testing strategy documentation so unit, integration, and E2E coverage guidance remains present and reviewable.
Changes
Added a dedicated validator for the testing strategy document in validate-testing-strategy.ts
Added regression tests in validate-testing-strategy.test.ts
Wired the validator into package.json via npm run validate:testing-strategy
Updated TESTING_STRATEGY.md and README.md to document the enforcement step
Testing
Ran: npm run validate:testing-strategy
Ran: npx vitest run validate-testing-strategy.test.ts
Notes
This closes the documentation/testing gap for issue #933 by making the testing strategy a checked repository artifact rather than a static document.