enzymejs/enzyme

Unmount and then wrapper.mount() again does not work properly

Open

#941 opened on May 13, 2017

View on GitHub
 (6 comments) (3 reactions) (0 assignees)JavaScript (19,979 stars) (2,016 forks)batch import
API: mountbughelp wantedquestion

Description

Enzyme: 2.8.2 React: 15.5.4

If we do wrapper.unmount(), and then wrapper.mount(), the component is not mounted properly. I can see an empty console output after mounting again.

Simple plain example as follows

class Foo extends React.Component {
  constructor(props) {
    super(props);
    
  }
  render() {
    return (
      <div className={this.props.id}>
        {this.props.id}
      </div>
    );
  }
}

const wrapper = mount(<Foo id="foo" />);

console.log("log before unmounting", wrapper.mount().debug()); //This logs the component properly

wrapper.unmount();

console.log("Log again after mounting", wrapper.mount().debug());//this logs empty component

Contributor guide

Tech stack
javascriptreact
Domain
testing
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic React knowledgeenzyme mount API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate the mount/unmount lifecycle in enzyme's ReactWrapper. Check the unmount method to see if it properly cleans up internal state. Look at the mount method to see if it reinitializes correctly after unmount. Consider if React's `unmountComponentAtNode` leaves residual state. Also review any similar issues or PRs linked.