You should aim to test components with shallow whenever possible
This will keep the test as narrow as possible
Testing the only necessary component and not the child/parent component
Using .instance() to get into the component methods
Another way to propogate to compoennt methods is using jest.spyOn(Input, "componentDidMount")
Try not to test connected components, but instead export the Class or Function, this will keep the test as small as possible, without having to mock the functionality of redux
In order to simualte change, click events on component
Ensure the selected element within the component has been selected
This might be .first() or .at(1) to select the appropriate element, or if there is a map of multiple elements that will be created by component to select only one
Testing of specific components
To test specific components use `npm run test /path/to/component`
To test all files under a folder use `npm run test /path/to/folder` this will however not test the subsequent child imported components that live outside of this folder
Stringify wrapper to get text from rendered component in order to use .toContain() to find specific text without checking entire html content
Otherwise you can use .html() in order to compare the entire html render
Test coverage on specific components
`npm run test /path/to/component -- --coverage`
This can cause issues if you are attempting to see coverage on everything related to this component and it's child components, so be careful when attempting to use this for stats
