in reality, its not usually software testing that's the problem. it's the project stakeholders who don't plan enough time to do adequate testing. it's the programmers who go way over their time estimates. it's the program managers (or similar role) who decide to ship a project even though it's not ready, and fix bugs later. it's the scope creep without schedule adjustments. it's companies who don't realize the value software testing gives.
In short, testing gets the shaft because of poor planning, poor resource management, and an unwillingness to delay projects or cut features when issues are found.
Lousy software testing damages many IT projects. When testing doesn’t uncover obvious problems that prevent software from operating as users expect, then failed projects are inevitable.
The consequences of brain-dead testing can be severe. For example, clothing retailer J.Crew recently had serious customer relationship problems when it deployed poorly tested software:
J.Crew reported weaker than expected second-quarter earnings due to severe problems following a website and call center upgrade. The fiasco caused cost the company $3 million in addition to lost sales and dissatisfied customers.
- Related: J.Crew: Failed upgrade hits financial performance
Last April’s massive IT failure at Heathrow Airport’s terminal T5 was also caused by brain-dead testing. In a moment of understatement adding insult to injury, British Airways CEO, Willie Walsh, commented:
We are working hard to tackle the difficulties we have had with the terminal’s baggage system. From time to time problems have developed that were not encountered during the extensive trials.
For another example of testing madness, look no further than Georgia Blue Cross and Blue Shield. Last August, the company wrongly released 200,000 medical records into the wild because of poor testing. A spokesperson told me:
There was a system change that was not comprehensively tested. We have already made changes to prevent it from happening in the future.
Click for five important tips to improve implementation testing. –>
