Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I regularly achieve 100% coverage of libraries using TDD, but not always, and there always seem to be parts of applications left over that are untested and uncovered.
Then there are the cases when you start with legacy code that has very few tests and very little coverage.
Please say what your situation is and what has worked that at least improved coverage.
I’m assuming that you are measuring coverage during unit testing, but say if you are using other techniques.
Delete code.
This isn’t snarky, but actually serious. Any time I would see the smallest amount of code duplication or even code that I couldn’t get to execute, I deleted it. This increased coverage and increased maintainability.
I should note that this is more applicable to increasing the coverage of old code bases vs. new code bases.