-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
unit testing at odds with queryCache #460
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.
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
Comments
please ignore my ignore statement as my tests are still hanging intermittently 😞 |
thanks for raising this - your suggestion to clear the cache is sufficient for me would be great if was built-in |
@KerrGrah how do you get access to |
@iamtekeste |
I can't believe it was that easy! Thank you. |
How can you use |
it's I find it best to wrap each component in a test in a new queryClient so that they are isolated and I don't need to clear things between tests. |
I'm having trouble working out the best way to test using react-query. I've looked at #113 but it doesn't solve my issues.
I've got a pretty good DI pattern for the actual fetching of data so that's not an issue. The issue I have is the queryCache persisting between tests. I can explicitly clear the cache before/after each test, but that doesn't help if you've got multiple async tests running in parallel.
Rather than importing a global queryCache, would it be helpful to store it in a react context, and then in your tests you can pass in a fresh cache for each test i.e.
or add it to the existing config provider.
The other issue I have is that my test runner (mocha) is hanging forever after the tests have run. I assume this is because of some internal timeouts/intervals/evenListeners or something. Am I missing some obvious way to stop them?
An example of an extremely simple test that's both failing and hanging:
(the reason it's failing is because a previous test has already called the useQuery hook and cached the response, if I ran a single test in isolation, it passes)
I think my bottom line of all this is I think react-query could do with some official ways to make unit testing easier (and keeping things isolated)
The text was updated successfully, but these errors were encountered: