Snapshot with ComponentDidCatch

[mitsuishihidemi]

💬 Questions and Help

Hi,

I am testing a HOC with componentDidCatch with Snapshot, and it is working but it displays an annoying message on my terminal. Do you know how can I hide that?

with-error.js

import React from 'react';
import { wrapDisplayName, setDisplayName } from 'recompose';

const ErrorPage = () => <h1>There is an error</h1>;

export default hasError => BaseComponent => {
    class WithErrorBoundary extends React.Component {
        state = { error: false };

        componentWillReceiveProps(nextProps) {
            if (hasError(nextProps) && !this.state.error) {
                this.setState({ error: true });
            }
        }

        componentDidCatch() {
            this.setState({ error: true });
        }

        render() {
            return this.state.error ? <ErrorPage /> : <BaseComponent {...this.props} />;
        }
    }

    return setDisplayName(wrapDisplayName(BaseComponent, 'ErrorCatcher'))(WithErrorBoundary);
};

with.error.test.js

it('should display the error page if it catchs an error', () => {
        const Component = withError()(() => {
            throw new Error('Error');
        });
        const subject = renderer
            .create(
                <Component />
            )
            .toJSON();
        expect(subject).toMatchSnapshot();
    });

The error message

I found this issue, but even with enzyme I got the same error.
enzymejs/enzyme#1255

react: ^16.3.2
jest: ^22.4.2

Thanks,

Please note that this issue tracker is not a help form and this issue will be closed.

For questions or help please see:

• The Jest help page
• Our discord channel in Reactiflux
• The jestjs tag on StackOverflow

[rickhanlonii]

You could override console.error and test for that error message

Please note that this issue tracker is not a help form and this issue will be closed.

We recommend using our discord channel or StackOverflow where there is an active jestjs tag for questions

[github-actions]

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.