|
The most
effective way to reduce risk is to start testing early in the development cycle
and to test iteratively, with every build. With this approach, defects are
removed as the features are implemented. The testing of the application is
completed shortly after the final features are coded, and as a result the
product is ready for release much earlier. Additionally, the knowledge of what
features are completed (i.e. both coded and tested) affords management greater
control over the entire process and promotes effective execution of the business
strategy. Testing with every iteration may require some additional upfront
planning between developers and testers, and a more earnest effort to design for
testability; but these are both inherently positive undertakings, and the
rewards are substantial.
There are several key advantages
gained by testing early and with every build to close the quality gap quickly:
 Risk is identified and reduced in the primary stages of development instead of in the
closing stages. ·
Repairs to problems are less costly.
The release date can be more accurately predicted throughout the project.
Results will be given by the way of requirement.
The product can be shipped sooner.
The business strategy can be executed more effectively.
Transparency established.
Artifacts can be reused for regression testing.
Not bound to any
particular vendor.
Key Measures of Software Quality Assurance
The key measures of a test include Coverage and Quality. Test Coverage is
the measurement of testing completeness. It is based on the coverage of
testing expressed by the coverage of test requirements and test cases or by
the coverage of executed code. Test coverage includes requirements based
coverage and code based coverage. Quality is a measure of the reliability,
stability, and performance of the target-of-test (system or
application-under-test). Quality is based on evaluating test results and
analyzing change requests (defects) identified during testing.
|
