Unfortunately, the word "testing" somehow equates to the quality of the software which it does not, not only to managers but those who have been taught to read about it and forced to repeat back it's list of advantages. It's a false sense of security found in a process that has minimal impact on the software performance and quality.
When you write a crappy source code that performs crappy, writing all the unit tests in the world won't save you. You simply increase the technical debt to future changes in the source code or design of the software.
Simply keeping things as simple as possible, focusing on quality and incrementally verifying along each step of the way saves far more time.
It always puzzles me how quality can be increased by writing more code around existing code of questionable quality.
When you write a crappy source code that performs crappy, writing all the unit tests in the world won't save you. You simply increase the technical debt to future changes in the source code or design of the software.
Simply keeping things as simple as possible, focusing on quality and incrementally verifying along each step of the way saves far more time.
It always puzzles me how quality can be increased by writing more code around existing code of questionable quality.