For a majority of companies, testing in the process of Software Development remains an unwanted devil they rather not to spend their money on. The question, we’re meeting the most frequently with is, Why should we spend money on something that will delay the development process, will cost us more, and we don’t even need it?
Well, while you’re right about the first two points, let me correct the third one you made – YOU NEED TO CONDUCT TESTING prior releasing your product. I could tell you a million of theoretical reasons why is that, but rather than that, let me share a story of one of our clients.
Our client, is the Energy services provider for highly regulated industries – such as hospitals, military bases, or big factories. The company approached us when their call centre suddenly received overwhelming number of complaints from their clients. The customers were charged twice, sometimes multiple times for the consumption, the data were missing, or were incorrect. As we speak about highly regulated industries (hospitals, military, etc.), this was a huge issue. Our client engaged its employees and assigned them double shifts to deal with the complaints. They engaged their accounting team to MANUALLY check ALL invoices that were issued, correct the duplicates, and issue the respective documents, fix them in their system, etc… Because it was obvious, that the error was triggered by the glitch within the existing systems, ALL corrections had to be done manually, employing dozens of employees. Needless to say, the reputation was already damaged, and the trust shaken.
When we got on site, we started as usual – with mapping all processes and systems within the complicated business hierarchy. We identified that the client used a central accounting system consisting from 10 independent modules feeding data to it. The IT system was developed externally, and part of the agreement between our client and their system developer was that it was our client’s responsibility to perform the acceptance testing prior any live installation and changes to the system. Because it was expensive, and time consuming, our client skipped the testing part, and implemented changes straight to the live environment. The system crumbled, recorded data incorrectly, and what’s more, this simple bug triggered a chain of events that proved to be catastrophic long-term. Not only our client had to spend a lot of extra financial resources to get their employees to fix what was already wrongly issued, but this “simple” mishap caused unrepairable damage to their reputation, and the mass exodus of their customers.
We came on board as independent solution-provider, and through the rigorous Testing methods, we identified what was the root-cause of the issue, fixed it – and voila – the business could go on as usual. Of course, only it was not anymore, a business as usual. You know, how it goes with the trust and reputation – it takes very long to build it up, but can be lost within a few minutes.
So, going back to our Hamletian question from the beginning of this article – To test or not to test? To test, of course. We are not saying this only because we want to “catch you” on our sales pitch, but because, as you see from the example of our client, trying to save some time and money in the development process, can cost you much more if things go wrong – and not only in the sense of money.
It’s true that often, your company needs a testing functionality only a short-term – with establishing new functions, or implementing new modules. It might seem like a burden to try to find someone on the market that would be able to help you a short term, to go through a burden or an interview process, and then – well, what will you do with them after the Testing part is over, all is working well, and you have no more assignments for your testing team? Plus, let’s face it – QA Testers are something of a “hot stock” recently. The moment they are available on the market, they are probably already gone, that’s how big is a demand after their services. Well, we know all that, and still – we’re able to help you.
Testing and Quality assurance is one of the flagship services we provide for our clients, and if you’re in need of a such service, don’t hesitate to get in touch with us. As you could see demonstrated on the example of one of our clients, the stakes are too high to neglect this part of the Software Development.