Friday, 01 May 2015 20:49

Why Test? Featured

Rate this item
(5 votes)

The purpose of testing is to ascertain that the product is built to its specifications and a quality product is released to the consumers.

Testing is an important step but we seem to be caught up in the cost, ROI, and measuring quality of the testing organizations to the extent that the basic premise of why we test is lost.

The goal of testing is to ensure the product is built to its specifications, not to run all tests and find tons of defects. Techniques, technologies and process can be employed to test faster, better and more accurately.

This is the ubiquitous SDLC as we all have known it and an Agile adaptation of it.

We could have the greatest idea and build the best product but with no feedback loop, we’ll be in a bubble and not ready for real launch. Let’s admit we all make mistakes. Mistakes range from frivolous, unimportant to expensive and significant ones. We need someone to validate our work. The testing team in an organization fulfills this role. Testers emulate user experience providing valuable feedback in the software lifecycle.

The downside of not testing can range from low revenues, customer frustration, cost to the company, to reputational damage.

Some publicized costly bugs are:

Toyota Bad Brakes: When Toyota recalled more than 400,000 of its hybrid vehicles in 2010, it wasn't because of a mechanical issue. The cars, including Toyota's Prius line, had a software glitch, which would cause a lag in the anti-lock-brake system. Cost to Toyota is estimated to be $3 Billion

Knight Capital Group Loses Nine Figures in 30 Minutes: Between 9:30 a.m. and 10 a.m. EST on August 1, 2012 the company’s trading algorithms got a little buggy and decided to buy high and sell low on 150 different stocks. By the time the bleeding had stopped, KCG had lost $440 million on trades.

There is no bug-free software. We need to ensure the released software works for one and for hundreds and for millions of users. This is the final line of defense a company has before it faces its customers. The defects will ultimately be found by the internal team or the end-users – the choice is yours!



Read 239 times Last modified on Monday, 04 May 2015 14:31