*"Testing Dynamics CRM" article corrections

We tend to build in pieces. Imagine building a car, creating the body, wheels, engine, brakes ... etc. Only to discover, after going to production, that customers are complaining about measly acceleration. At that stage, you have to recall, make adjustments, and deploy again -- a huge waste of time and money. Only to fail again due to another unforeseen issue. Testing every aspect of the product before even building a single car could have avoided such a massive hit; test the engine alone under the expected load.

Most customers I have met expect a “bug-free” solution, whose trust is lost gradually with every issue popping up. Regardless of customer’s expectations in this area, there’s an art in outweighing the risk vs the reward of “seeking” exhaustive testing for the sake of a successful project. Targeting likely sources of the most severe cause of issues for testing could striking the golden balance in this case