Like anything else, there's a balance. Don't let yourself go all-out to ensure you have 100% test coverage of every line of code. There is always a cost-benefi

Like anything else, there's a balance. Don't let yourself go all-out to ensure you have 100% test coverage of every line of code. There is always a cost-benefit argument that should be replaying in your head over and over. If it's a critical part of your application, then make sure it has test coverage. If it's a simple part that's basically just doing CRUD operations with almost no custom code, it's probably not worth worrying about in the short term. Just make sure you cover the primary flex points and custom algorithms or libraries, and you'll be fine.