I've been recently asked this question in an interview and this was my answer:
For ReactJS in particular, there are many testing libraries that allow you to do shallow rendering (enzyme for example), that means that if you have a composed component, the test won’t actually render that inner component so you can’t make assertions on that. If you want to cover those internal components you need to write specific tests for each part.
<div> <Form> <Username /> <Email /> </Form> </div>
With this structure, if you want to write a test for this component, the first
div will be rendered but the custom
Form component won’t, neither the
If you follow this pattern, you will soon end up with a set of pure unit tests that are really confusing and hard to follow.
Kent C. DoddsThe less your tests resemble the way your software is used, the less confidence they can give you.02:35 AM - 18 Feb 2018
Tests should resemble the way the software is used. Even though is not pure unit tests (technically you can call it integration test), at the end of the day the only thing that matters is that you can ship your app with confidence.