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
TypeError: Function.prototype.name sham getter called on non-function
● <ErrorBoundary> component › should render with message if error occour
TypeError: Function.prototype.name sham getter called on non-function
20 | );
21 |
> 22 | expect(wrapper).toMatchSnapshot();
| ^
23 | });
24 |
25 | it("should render if error occour", function() {
at Function.getName (../node_modules/function.prototype.name/implementation.js:31:9)
at displayNameOfNode (../node_modules/enzyme-adapter-utils/build/Utils.js:156:95)
at ReactSixteenAdapter.displayNameOfNode (../node_modules/enzyme-adapter-react-16/build/ReactSixteenAdapter.js:605:62)
at typeName (../node_modules/enzyme/build/Debug.js:60:43)
at internalNodeToJson (../node_modules/enzyme-to-json/mount.js:70:31)
at mountToJson (../node_modules/enzyme-to-json/mount.js:93:12)
at Object.<anonymous>.exports.default (../node_modules/enzyme-to-json/index.js:14:32)
at Object.print (../node_modules/enzyme-to-json/createSerializer.js:22:40)
at printPlugin (../node_modules/pretty-format/build/index.js:287:16)
at prettyFormat (../node_modules/pretty-format/build/index.js:485:16)
at Object.throwingMatcher (../node_modules/expect/build/index.js:320:33)
at Object.toMatchSnapshot (src/components/molecules/ErrorBoundary/ErrorBoundary.test.jsx:22:19)
Based on your SO post, you should indeed be explicitly naming your class, but also, this is because your error fallback is a string - and enzyme does not yet support rendering non-elements (see #1149).
For now, you can make your error fallback be a React fragment.
Current behavior
When run with
--coverage
i get this error..`
If I not run with coverage, everything works fine
Question posted on Stackoverflow
Expected behavior
Run tests with coverage without error
Your environment
API
Version
Adapter
The text was updated successfully, but these errors were encountered: