100% Coverage in Test-Driven Development

preview_player
Показать описание
Don't just aim for 100% code coverage in test-driven development. Code coverage is not a perfect metric. Aim for balance instead. What does that mean? Learn more in today's short.

#arjancodes #softwaredesign #python
Рекомендации по теме
Комментарии
Автор

I think near 100% coverage is more useful for products like 3rd party libraries, i.e. psycopg2 rather than usual software products at regular companies

josewilhelm
Автор

I used to be a supporter of full coverage, but ultimately discovered it's a bad metric. Perfection there leads to bloated tests and hypothetical over real-world cases while chasing that 100% mark.

ClifBratcher
Автор

From my experience 100% coverage helps you to reduce crashes. If code in compiled languages run, you know every line of code is "legal", but that might not be true in Python.

JorgeLuis-tsqp
Автор

using a framework like fastAPI which uses dependency injection make it really easy to reach 100% coverage (skipping external services off course) makes development so much easier and enjoyable.

doronvaida
Автор

For many projects I've seen it would have been important to test at all 😅😅😅

marcotroster
welcome to shbcf.ru