Test to Destruction
June 14, 2010
You have been around long enough to know your programmers don’t test to find problems. Programmers test to prove their stuff works. You have also been bitten by the problems this causes. Systems that work in the lab fail in front of a customer. You lose business, you lose customers, you lose confidence. Why don’t your programmers test till the system breaks? Why can't they find every problem, before it becomes your problem? Wouldn’t it be better if your systems were tested to destruction before being released in the real world?
| < Newer Post | Older Post > |
|---|
Print this page |
E-mail this page