I agree, but if testing is not part of your routine starting with "test absolutely everything" will result overwhelming and you may just give up entirely.
A good approach is to start where it hurts. Then add tests for every bug you find. Then if you still have time and budget feel free to go all in!
It also depends if you are building a library (I'd test as close to 100% as possible in that case) or a Gatsby website (I'd maybe only test a few UI components)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.