5 ms·
Much of what passes for testing is a near-criminal waste of corporate resources. I've seen so much rubbish test code.
by encoderer 12y ago
Much of what passes for testing is a near-criminal waste of corporate resources. I've seen so much rubbish test code.
- Tyguy7 12y agoI have similar experiences.
- UK-AL 12y agoUnit Tests are a god send when you have good coverage on a legacy large project. Refactor code, and it gives you that much more confidence you have not broken anything. They're seriously useful mid-later stages of a project, which is probably why startups devs aren't doing them...
- donchipotle 12y agoI think what they are saying is the kind of tests they see in a corporate environment are not the kind that add any value to the refactoring process (or worse, inhibit it).
- jakub_g 12y agoTests are a great thing when everyone involved understands their value. In my former team we had a big number of unit & integration tests that saved my ass many times. On the other hand, when the team has a KPI "we need a big test coverage!" and people are lazy or simply bad developers, you end up with a code like try { runTheWholeApp() } catch (e) {} assertTrue(itRan)
- ZeroGravitas 12y agoMutation Testing can test your tests in these situations. Well actually if the organization is that dysfunctional it's probably game over, but Mutation Testing can catch you when you do this accidentally.
- Cymen 12y agoOne could say the same about non-test code.