fix(change): no longer using Simulate.change

In real applications, your `onChange` handler wont be called if the
value did not change, so the tests shouldn't either. This is another
step toward us not using Simulate at all.

When using `fireEvent.change` make sure that you're setting the value
to change to via: `{target: {value: 'the value'}}` as the second arg.

BREAKING CHANGE: If you used the old form of value changes you'll need to update your code to the new form:

Before:

```js
formField.value = newValue;
fireEvent.change(formField);
```

After:

```js
fireEvent.change(formField, {target: {value: newValue}});
```

Author: Kent C. Dodds

src/__tests__/events.js

@@ -30,7 +30,7 @@ const eventTypes = [
   },
   {
     type: 'Focus',
-    events: ['change', 'input', 'invalid'],
+    events: ['input', 'invalid'],
     elementType: 'input',
   },
   {
@@ -154,3 +154,12 @@ eventTypes.forEach(({type, events, elementType, init}) => {
     })
   })
 })
+
+test('onChange works', () => {
+  const handleChange = jest.fn()
+  const {
+    container: {firstChild: input},
+  } = render(<input onChange={handleChange} />)
+  fireEvent.change(input, {target: {value: 'a'}})
+  expect(handleChange).toHaveBeenCalledTimes(1)
+})

src/index.js

@@ -48,7 +48,7 @@ function cleanupAtContainer(container) {
 }
 
 // fallback to synthetic events for React events that the DOM doesn't support
-const syntheticEvents = ['change', 'select', 'mouseEnter', 'mouseLeave']
+const syntheticEvents = ['select', 'mouseEnter', 'mouseLeave']
 syntheticEvents.forEach(eventName => {
   document.addEventListener(eventName.toLowerCase(), e => {
     Simulate[eventName](e.target, e)