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.
The best of ZDNet, delivered
ZDNet Newsletters
Get the best of ZDNet delivered straight to your inbox
