-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Components are being rendered as <WrappedComponent> on CI, but not locally #640
Comments
Rendering the snapshot with |
Are you using a different jest version locally as to your CI? Just a guess, seems like you are getting a new version of jest on your CI, and an old version locally. |
Also, this is very much not an enzyme issue. So i'm going to close this issue. We can keep talking about it and i'll try to help. But again, not an enzyme issue. |
Ok thanks :). As for the version discrepancy, I'm using yarn (with a yarn.lock) to install my dependencies both locally and on my CI. So it should be completely similar. But maybe something's being cached, I'll double-check that. |
So I found the problem: on my CI server I actually run |
I'm getting different results based on whether I run my snapshot tests on my CI server vs locally. I'm using enzyme and enzyme-to-json to create snapshots. Locally the tests all pass, but when I push them to my remote the CI test fails because it renders the snapshot differently. The test is:
The output of the failing test is:
As you see, the react component names are replaced by
WrappedComponent
when testing on the CI. What causes this? It should be rendering in exactly the same manner right?The text was updated successfully, but these errors were encountered: