Point of Stop Testing: Ensure Success Within Limited Budget and Stringent Deadlines
Quality Assurance (QA) teams can effectively test complex applications, and work within a limited budget and stringent deadline by relying on scientific data for ‘testing to release.’
QA organizations can determine the Point Of Stop in Testing (POST) to achieve consistency in the quality of applications based on historical data, business imperatives and the sequence of test cases for execution.
In an article published in T.E.S.T magazine, Infosys’ experts discuss how POST helps QA teams draw the line between knowing when to stop testing and testing continuously to achieve 100% coverage -
- Criticality to business – QA teams must focus on applications that are used frequently, have financial and legal implications, and the potential to dilute brand equity. Such applications must be tested based on past defect discovery rate and the average time required for testing.
- Sequencing of test cases – QA teams must first run test cases of key application features to be released at the outset. It ensures application quality as well as savings in time and cost.
Read the article
The article first appeared in the December 2009 issue of T.E.S.T magazine.
Authors
Stephen Sanjay Desmond Emmanuel, Delivery Manager, and Head, IVS Tools, IP and Services (TIPS), Independent Validation and Testing Practice, Infosys Limited. Stephen currently anchors the innovation, R&D and solutions areas. He can be reached at
Sindhu Mahesh, Project Manager, IVS Tools, IP and Services (TIPS), Independent Validation and Testing Practice, Infosys Limited. Sindhu is the Service Lead for Regression Testing Service of TIPS. She also manages SOA automation testing project for a leading bank in the U.S. Sindhu can be reached at
Related Reading
Models for Evaluating Review Effectiveness ,