-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Automated Testing: Unskip tests blocked by Enzyme support of React 16.3 #7005
Comments
I just wanted to add that all tests that we skip currently are blocked by Enzyme's upgrade. |
Ya although its a pain, the more you work |
Also worth noting that under the hood enzyme uses the various react test utilities. |
Can we make sure to cross-reference pull requests meant to be addressing (or partially addressing) this issue. |
As far as I know there's only one skipped (unit) test now. |
Which pull requests are those? I'd like to keep record here for historical purposes. |
We no longer use Enzyme. |
Previously: https://github.com/WordPress/gutenberg/pull/6527/files#r185974677
We currently skip tests which rely on
React.forwardRef
because they are not supported yet by Enzyme:gutenberg/components/button/test/index.js
Lines 106 to 118 in 400f8fc
This is tracked by the Enzyme project at enzymejs/enzyme#1604
Once the above issue is closed and Enzyme produces a new release introducing support for
React.forwardRef
, we should remove the workarounds introduced by #6527 .Open questions:
Button
have tests which need to be updated?The text was updated successfully, but these errors were encountered: