![]() All this in turn leads to writing higher quality code to begin with (more modular, cleaner contracts in their APIs, more manageable code reviews, etc.). For example, teams that give code coverage priority tend to treat testing as a first class citizen, and tend to bake stronger testability into their product design, so that they can achieve their testing goals with less effort. It is an open research question whether code coverage alone reduces defects, but our experience shows that efforts in increasing code coverage can often lead to culture changes in engineering excellence that in the long run reduce defects. ![]() Instead, use it in conjunction with other techniques to create a more holistic assessment of your testing efforts. You must treat it with the understanding that it’s a lossy and indirect metric that compresses a lot of information into a single number so it should not be your only source of truth. It does not require significant human interaction, it applies universally to all products, and there are ample tools available in the industry for most languages. ![]() It is not a perfect measure of test quality, but it does offer a reasonable, objective, industry standard metric with actionable data. Code coverage provides significant benefits to the developer workflow. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |