3 ms·
Not if a simple test requires rewriting hundreds of tests (aka "fragile tests"). Yes, one shouldn't be writing fragile tests, but usually from what I seen at p
by deepsun 4y ago
Not if a simple test requires rewriting hundreds of tests (aka "fragile tests").
Yes, one shouldn't be writing fragile tests, but usually from what I seen at projects with great test coverage, is that it often slows bugfix releases, and especially any bigger changes, as it's very wearisome to also change hundreds of tests.
So I believe there should be some balance between tests/code ratio, as well as attention paid to tests brittleness.
- 2rsf 4y agoDefinitely, some real world cases research show that this balance stands around 80% for unit tests- you don't earn more quality as you add more test above that.
- deepsun 4y agoLast time I heard 80% ratio is optimal for Java, but any dynamic typing language (JS, Python, Ruby) it's around 100% test LOC / code LOC.