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
I'm running into an issue where one of my third-party components uses refs.
This issue has already been explained and closed in #1332, but what wasn't provided was a workaround.
As it stands, snapshot testing is totally broken for the component in question, as well as its parent components. The component in question is a third-party component for integration with MapBox - is there a way to mock out the ref?
How about simply not testing the MapBox component, and mocking out that component for its parent components? I can live with that component not being tested, but I need to be able to test the components further up the tree.
Would appreciate any guidance. Recently came back to Jest after almost 2 years, and it's gotten tons better since then :)
Node v6.2.2, NPM 3.9.5
The text was updated successfully, but these errors were encountered:
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.
Hi,
I'm running into an issue where one of my third-party components uses refs.
This issue has already been explained and closed in #1332, but what wasn't provided was a workaround.
As it stands, snapshot testing is totally broken for the component in question, as well as its parent components. The component in question is a third-party component for integration with MapBox - is there a way to mock out the ref?
How about simply not testing the MapBox component, and mocking out that component for its parent components? I can live with that component not being tested, but I need to be able to test the components further up the tree.
Would appreciate any guidance. Recently came back to Jest after almost 2 years, and it's gotten tons better since then :)
Node v6.2.2, NPM 3.9.5
The text was updated successfully, but these errors were encountered: