Testing Patience
by in Feature Articles on 2013-04-24The process used to test new applications before delivering them to the user base at Eric's company had never been particularly formal. This is not to say that there was no process at all. Of course there was. After all, what kind of a company would develop software and then release it to the user base without running it through some testing. But 'rigorous testing' and 'robust validation' were not phrases used within his organization. Neither was 'successful rollout' or 'satisfied users', but that's a story for another day.
One reason for the lack of formality was that the company didn't feel that having dedicated testing resources delivered sufficient benefit for the cost. Shouldn't developers just write code that didn't have any bugs? Was that so hard?