4 ms·
A huge benefit of deleting tests isn't merely the reduction in maintenence but the reduction in "conceptual drag". Tests cause design decisions to get baked int
by gfodor 4y ago
A huge benefit of deleting tests isn't merely the reduction in maintenence but the reduction in "conceptual drag". Tests cause design decisions to get baked into code to a higher degree than if the same decisions were made in a codebase without tests.
Tests certainly can be valuable for verifying the scope of changes, but they're not the only way to do this. I could imagine supporting the process of delete-as-you-go testing if you could convince me that whatever you are doing to identify regressions works just as well as the test suite would.
- twodave 4y agoI'm not sure you can separate "identify regressions" and "test suite" into different buckets. I'll concede that if you can, it'd be an acceptable replacement--assuming, of course, that it doesn't add more friction than it replaces.