React uses its own events system with SyntheticEvents (prevents browser incompatabilities and gives react more control of events). Using TestUtils correctly creates such a event which will trigger your onChange listener. The dispatchEvent function on the other hand will create a “native” browser event. But the event handler you have is managed by react and … Read more
The underlying problem is How to test console.log? The short answer is that you should replace the console.{method} for the duration of the test. The common approach is to use spies. In this particular case, you might want to use stubs to prevent the output. Here is an example implementation using Sinon.js (Sinon.js provides standalone … Read more
This is a recurrent question. I’m sharing my own code with 100% passing tests which cover 100% of my source code. My component looks like this MySelectComponent({ options, onChange }) { return <div data-testid=”my-select-component”> <Select className=”basic-single” classNamePrefix=”select” name=”myOptions” placeholder=”Select an option” options={options} onChange={e => onChange(e)} /> </div>; } The reason I’m adding a wrapper on … Read more