[rnd33]

> "Yes, it's just an API change, but it requires 50 new test cases and impacts 120 existing test cases",

"See, that's exactly why we shouldn't write any/so many tests!" - A product owner I know...

[jlg23]

He might have a point if a simple API-change impacts 170 test cases. This sounds suspiciously like "no functional tests but let's go for 100% coverage with unit tests" - not necessarily the efficient thing to do, from a management perspective.

[dasil003]

"Manual QA then? That will be even slower than automated..."

[sidlls]

That product owner might have a good point. Far too many engineers I know think 100% coverage is a reasonable goal and spend way too much time writing unit tests that don't add much value or worse add negative value.