event.currentTarget not working when using mount

Current behavior

currentTarget not working when using mount

const wrapper = mount(<input type="text" onChange={(e)=> console.log(e.currentTarget.value)}/>)

wrapper.simulate('change', {currentTarget: {
  value: 'Hello'
}});

currentTarget working when using shallow

const wrapper = shallow(<input type="text" onChange={(e)=> console.log(e.currentTarget.value)}/>)

wrapper.simulate('change', {currentTarget: {
  value: 'Hello'
}});

Hello

Expected behavior

const wrapper = mount(<input type="text" onChange={(e)=> console.log(e.currentTarget.value)}/>)

wrapper.simulate('change', {currentTarget: {
  value: 'Hello'
}});

Hello

Your environment

API

• shallow
• mount
• render

Version

library	version
enzyme	3.1.15
react	16.6.3
react-dom	16.6.3
react-test-renderer	16.6.3
adapter (below)	1.0.3

Adapter

• enzyme-adapter-react-16

[ljharb]

I would suggest avoiding .simulate - it doesn’t faithfully simulate anything. Instead, manually invoke the desired prop - ie, wrapper.prop('onChange')(fakeEvent).

[wyqydsyq]

@steveHornseyDeveloper triggering the onChange prop is the proper way to do it; if you’re not using something like webdriver to make an actual click, then you’re not getting any value out of implicitly calling onChange by using simulate.

Perhaps if triggering the desired handler from the mounted component’s props is the “proper” way to do it, then this fact should be documented somewhere?

Searching Google for “enzyme trigger event” gives results where every link on the first page tells you to use .simulate(), the first two of which are links to the official Enzyme docs.

Further, all the examples of triggering events in Enzyme’s official docs suggest to use .simulate().

Even just mentioning what you’ve said in this issue thread under the common gotchas of this function would be a lot clearer than users having to dig through threads to find this information.