Why is software testing often ignored?

Abhimanyu Grover
January 5, 2011
A survey conducted few years back concluded that 82% of managers believed that poor software testing was costing them significant amount of money.

If stats are so clear then why testing is still ignored? Can't we learn from it? My answer.... yes, but not without strategical thinking.

Here's what happens while project development. You allot a 60-day timeline to a project, and leave last 2 weeks for testing. Last day of development, your developer comes to you crying and tells you that he has discovered a 'hack' which should be fixed otherwise we cannot  "<insert any excuse here from your experience>" (examples from my personal experience: 'we'll be unable to scale up', 'we'll risk with security', 'whole software will explode at client's location'). And then you go on and rather than dedicating last 2 weeks on testing, you are still in process of 'development' which is now being done at the expense of testing. This is all fault of Waterfall model which taught you to do one thing at a time and sometimes lack of "testing as a process" in your own development methodology. Test Collab on the other hand encourages you to use agile methodology so from the day-1 of your project development, you are free to communicate with your team mates about your test strategy.