My limited number of tests seem to suggest that the answer is no. I'm writing a unit test for a parent level React component (aka a controller view) that has a dependency on a store. However, Jest is not providing an auto-mock for the store, as the documentation suggests it should, and is instead calling the real implementation.
Is this a bug or by design? If the latter, is the takeaway that unit testing react components is not desirable?
Automocking works just fine when testing a CommonJs module; it's just not working for react components.