Software Quality Assurance Testing is an integral and critical phase of any software development project. Developers and testers must ensure that
• Newly developed products or product enhancements meet functional and performance requirements
• The products are reliable and able to operate consistently under peak loads.
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
Subscribe to:
Post Comments (Atom)
1 comment:
Good list of advantages to be gained by testing early. If the testers are engaged early in the product life cycle I'd also add that there is the opportunity to help ensure that the customer is more likely to get what they are expecting. I mean if the software tester is working on the customers behalf then they should be able to spot errors and ommisions in the requirements specification well before coding even starts.
William Echlin
www.SoftwareTesting.net
Post a Comment