Add @testing-library as foundation for testing user-facing components #7437
Conversation
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
Collaborator
Cloudflare Pages deployment
|
|
Contributor
Author
|
If the core team is okay with implementing Testing Library, I'll create follow-up MRs for tests. |
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.
This MR provides a basic example of
@testing-libraryby https://testing-library.com/docs/guiding-principles in practice as a standard for testing user-facing components.Changes
@testing-library/jest-domand@testing-library/reactsrc/apps/dashboard/components/drawer/sections/AdvancedDrawerSection.test.tsx