"Proper testing" is often introduced, in CS courses, as 100% Test Coverage cargo cultism. Which is really a error-prone and unproductive way of ensuring Correct

"Proper testing" is often introduced, in CS courses, as 100% Test Coverage cargo cultism. Which is really a error-prone and unproductive way of ensuring Correctness in the software beyond the guarantees offered by the programming language. Most SW orgs should not waste time on test coverage metrics. On the other hand, we can look at SW testing as "building a robotic user that will catch errors before real users". This approach is far more intellectually-engaging, productive and gets SWEs in touch with the product. That is to say, SWEs aren't shit at "testing", they are shit at product, because product is virtually omitted in traditional CS curricula.