We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I attempted to perform the following two tests of a component in order using MockedProvider:
mocks={[]}
Intended outcome: Either both tests pass or only the first test passes.
Actual outcome: The second test fails unless the tests are performed in the opposite order
How to reproduce the issue:
MockedProvider
mocks
setTimeout
it('succeeds', () => { const component = renderer.create( <MockedProvider mocks={[]}> <App /> </MockedProvider> ); }); it('fails', async () => { await new Promise((resolve) => setTimeout(resolve, 0)); });
You can see a longer reproduction closer to the actual code as well as a runnable version of the above in this fork of the error reproduction repository.
Versions
System: OS: macOS 10.15.4 Binaries: Node: 12.13.1 - ~/.nvm/versions/node/v12.13.1/bin/node Yarn: 1.21.1 - ~/.nvm/versions/node/v12.13.1/bin/yarn npm: 6.12.1 - ~/.nvm/versions/node/v12.13.1/bin/npm Browsers: Chrome: 83.0.4103.61 Firefox: 72.0.2 Safari: 13.1 npmPackages: @apollo/client: ^3.0.0-rc.0 => 3.0.0-rc.0
The text was updated successfully, but these errors were encountered:
Update @wry/equality to improve undefined property handling.
dd77cae
See benjamn/wryware#21 for explanation and motivation. Should help with #6771, #6803, #6688, #6378, and #7081, and possibly other regressions that began in @apollo/[email protected].
Update @wry/equality to improve undefined property handling. (#7108)
0cf81cb
#7108 should have fixed this - let us know if not - thanks!
Sorry, something went wrong.
No branches or pull requests
I attempted to perform the following two tests of a component in order using MockedProvider:
mocks={[]}
Intended outcome:
Either both tests pass or only the first test passes.
Actual outcome:
The second test fails unless the tests are performed in the opposite order
How to reproduce the issue:
MockedProvider
with an emptymocks
list.setTimeout
promise.You can see a longer reproduction closer to the actual code as well as a runnable version of the above in this fork of the error reproduction repository.
Versions
The text was updated successfully, but these errors were encountered: