By Ben Linders
The serie on “What Drives Quality” continues. Previously covering Requirements Quality, Architecture and Design Quality Coding Quality, and Review and Inspection Quality, this post covers Testing. Understanding what drives quality enables you to take action before problems actually occur, thus saving time and money.
Testing covers many ways of verifying and validating the product. For example it can start with functional testing, followed by system testing, integration testing up to and including release testing. These are just examples, most companies define their own testing stages. There is a lot published on testing, I guess it’s number 1 in Quality Assurance wrt publications, conferences, and professional network. However, QA is not testing, and many of the defects that are found with testing could have been found earlier in a more economical way. But ok, testing is important to quality, so that’s why this blog posting looks at how testing can drive and contribute to better product quality.
Some factors that influence testing quality are: