X

Infosys Validation Solutions

Features & Opinions

Point-of-stop testing: ensure success within a limited budget and stringent deadlines

Quality assurance (QA) teams can effectively test complex applications, and work within a limited budget and stringent deadlines 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 TEST 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 rates, 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.

The article first appeared in the December 2009 issue of TEST magazine.

Authors

Stephen Sanjay Desmond Emmanuel

Stephen Sanjay Desmond Emmanuel, Delivery Manager, and Head, IVS Tools, IP and Services (TIPS), Independent Validation and Testing Practice, Infosys
Stephen currently anchors the innovation, R&D and solutions areas. He can be reached at

Sindhu Mahesh

Sindhu Mahesh, Project Manager, IVS Tools, IP and Services (TIPS), Independent Validation and Testing Practice, Infosys
Sindhu is the service lead for Regression Testing Service of TIPS. She also manages the SOA automation testing project for a leading bank in the U.S. Sindhu can be reached at

Related reading

Models for evaluating review effectiveness

Share the page

  • Tweet
  • Share on Facebook
  • Share on LinkedIn
  • Google+