[Docs]: add a guide for testing

[sonicolasj]

What is the new or updated feature that you are suggesting?

Please add a testing guide to make it clear how to unit test components using react-router!

Why should this feature be included?

There was a testing guide for v5, which was very helpful!

[ptim]

Here's a guide from React Testing Library for v6:
https://testing-library.com/docs/example-react-router/

[github-actions]

This issue has been automatically marked stale because we haven't received a response from the original author in a while 🙈. This automation helps keep the issue tracker clean from issues that are not actionable. Please reach out if you have more information for us or you think this issue shouldn't be closed! 🙂 If you don't do so within 7 days, this issue will be automatically closed.

[halcarleton]

Here's a guide from React Testing Library for v6: https://testing-library.com/docs/example-react-router/

This guide does not include instructions for testing data routes. I have tried to find a way to adapt the guide to work with data routes but have not had any success.

[maruhgar]

Here's a guide from React Testing Library for v6: https://testing-library.com/docs/example-react-router/

This guide does not include instructions for testing data routes. I have tried to find a way to adapt the guide to work with data routes but have not had any success.

I just submitted a PR after raising an issue . You can refer to this working example, which uses vite and vitest. It is the v6 example extended for v6.4 using createBrowserRouter and action and loader scenarios. Hope this helps.

[busticated]

it would be super-helpful to have docs around testing components which invoke useFetcher() specifically. short of mocking it out entirely, i haven't had much luck sorting it out on my own.

edit: and useSubmit() too 😮‍💨

Error: useSubmit must be used within a data router.  See https://reactrouter.com/routers/picking-a-router.

[weotch]

@busticated this fixed my issues, fwiw: remix-run/remix#8403 (comment). I made sure I only had one version of react-router-dom in my lock file.