Skip to content

Docs: Fix typo in package name in interaction testing #35103

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Sidnioulz merged 5 commits into from
Jun 17, 2026
Merged

Docs: Fix typo in package name in interaction testing #35103

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
fb1999d
Fix typo in interaction testing documentation
Juicy1011 Jun 9, 2026
52cf43e
Merge branch 'next' into patch-1
jonniebigodes Jun 9, 2026
fdf7d4b
Merge branch 'next' into patch-1
jonniebigodes Jun 9, 2026
34cbca9
Merge branch 'next' into patch-1
jonniebigodes Jun 9, 2026
edb2dd8
Merge branch 'next' into patch-1
jonniebigodes Jun 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/writing-tests/interaction-testing.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ The subjects are listed here, with links to their full Testing Library documenta

<Callout variant="info" icon="💡">

Note the order of this list! We (and [Testing Libary](https://testing-library.com/docs/queries/about#priority)) highly encourage you to query for elements in a way that resembles the way a real person would interact with your UI. For example, finding elements by their accessible role helps ensure that the most people can use your component. While using `data-testid` should be a last resort, only after trying every other approach.
Note the order of this list! We (and [Testing Library](https://testing-library.com/docs/queries/about#priority)) highly encourage you to query for elements in a way that resembles the way a real person would interact with your UI. For example, finding elements by their accessible role helps ensure that the most people can use your component. While using `data-testid` should be a last resort, only after trying every other approach.
Comment thread
jonniebigodes marked this conversation as resolved.

</Callout>

Expand Down