We want to write maintainable tests that give you high confidence that your components are working for your users. And for the Front-End we need to focus on only two targets for our tests: The end-user who interacts with your component in the browser.
The developer who renders and uses your component in the code. So long as your tests serve those two, then they have reasons to exist. But far too often we introduce a third user, the test user. This user usually tests stuff that neither our consumers nor our business care about (Ex: testing implementation details).