3 ms·
I've been considering writing the exact opposite of this blog post. Working with an application that has maybe 70% code coverage but missing testing around some
by blacktriangle 6y ago
I've been considering writing the exact opposite of this blog post. Working with an application that has maybe 70% code coverage but missing testing around some major functionality like reports. We've hit the point where the rate at which we add new features has slowed to a halt as we manually have to test a bunch of stuff combined with a growing fear every time we push new functionality. Sadly we're so overcommitted on new features that we aren't devoting the time to going back and filling in more tests, but we're trying to slowly improve the situation rather than let it get worse.
Then to make it extra fun we inherited two native mobile companion apps built by contractors with 0 testing that nobody even wants to touch.
So yeah, I'm 100% joining the frantic about code testing camp. My immediate state of flow getting broken up is a small price to pay for being able to sleep on nights when we push new functionality to production.