Discussion on "Why reaching 100% Code Coverage must NOT be your testing goal (with examples in C#)"

Davide Bellone · 2024-08-28T10:23:04.598Z

Code Coverage is a valuable metric in software development, especially when it comes to testing. It provides insights into how much of your codebase is exercised by your test suite. However, we must recognize that Code Coverage alone should not be th...

I love the grounded reality of @harold_kendrickfx Mentorship program on instagram, despite the current economic recession I'm so happy withdrawing my $94k profits out of my investment with their platform 𝐰𝐭𝐬𝐩 𝗵im ✙𝟰𝟰𝟳𝟰𝟬𝟳𝟲𝟬𝟬𝟭𝟲𝟲..

Hello, if you do satvki, it is only on this site online, - registration the best sports betting girls on this site, it is definitely able to give you the same experience of the game that you are looking for, what is better than betting on your favorite team and when the game is over, in addition to positive emotions, you will receive money and the chances that you will win are very high, I actively win here.

I love to play on this site from Australia - royalreels11.com/, royal reels australia, I love to play on this site without a doubt the coolest site on which I play and win without any problems I play on slot machines that are on this site and there are many of them here, but I chose for myself those on which I like to play the most and you can also find them for yourself

What is your opinion about test-driven development and the role of test coverage in this context? As a TDD practitioner, I actually never calculate this metric.

IMHO, since TDD focuses too much on code implementation and is tightly coupled with the code (simply, method names and parameters must match), this metric still does not mean you're safe.

If your tool allows you to see the lines of code covered by tests, you can use it to see the parts of the code that are NOT covered by any test - then you can write, if necessary, some more tests.

However, in general I think that following the Test Diamond strategy is more beneficial (if you don't know what it is, here's a short introduction: code4it.dev/architecture-notes/testing-pyramid-vs… )

Davide Bellone Yes, I have read your article about the diamond strategy, and I feel it doesn't quite fit with TDD. Test-driven development isn't just about testing; it's more about the development process as a whole. However, I do agree with your point about the importance of integration and end-to-end tests—these are crucial in the TDD approach as well. I find it challenging and expensive to cover numerous cases with integration or e2e tests. As you mentioned in your example, many cases were left untouched, even with a simple scenario. This issue becomes even more pronounced in complex enterprise-level applications, where the number of variables and potential cases for integration tests grows exponentially.

Discussion

Why reaching 100% Code Coverage must NOT be your testing goal (with examples in C#)

Responses(1)

Recent in Forum

Search Hashnode

Why reaching 100% Code Coverage must NOT be your testing goal (with examples in C#)

Responses(1)

Recent in Forum