You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
Testing components with MockedProvider. Mock queries are written out added to MockedProvider along with a prop for handling the typename (since it isn't provided in the query).
I expect that by using only one of the two - addTypename={false} or removeTypename={true} - for all tests, the test should run correctly for all developers on their machines.
Actual outcome:
For myself, my test fails if I have the prop addTypename={false} in my MockedProvider, so I use removeTypename={true}. Another developer also writing tests finds that it fails if they use removeTypename={true} and instead need to use addTypename={false} to get the tests to run and pass.
Version
Both apps are running these versions:
apollo-client: ^2.0.3
react-apollo: ^2.0.1
The text was updated successfully, but these errors were encountered:
Intended outcome:
Testing components with MockedProvider. Mock queries are written out added to MockedProvider along with a prop for handling the typename (since it isn't provided in the query).
I expect that by using only one of the two -
addTypename={false}
orremoveTypename={true}
- for all tests, the test should run correctly for all developers on their machines.Actual outcome:
For myself, my test fails if I have the prop
addTypename={false}
in my MockedProvider, so I useremoveTypename={true}
. Another developer also writing tests finds that it fails if they useremoveTypename={true}
and instead need to useaddTypename={false}
to get the tests to run and pass.Version
Both apps are running these versions:
The text was updated successfully, but these errors were encountered: