Trimming the Test Suite

[article]
Using Coverage Analysis to Minimize Re-Testing
Member Submitted
Summary:

When you have 15 million lines of code to test, and you need to get a quality product to market as soon as possible, you need ways to streamline testing. This paper explores how to use Coverage Analysis System (CAS) data to determine the optimum set of automated tests to execute for a corrected defect.

When you have 15 million lines of code to test, and you need to get a quality product to market as soon as possible, you need ways to streamline testing. This paper explores how to use Coverage Analysis System (CAS) data to determine the optimum set of automated tests to execute for a corrected defect.

We have derived different methods using CAS data:  

  • selecting all of the tests that execute the modified source file
  • selecting the minimum number of tests that provide coverage for as many lines in the source file as have been executed
  • selecting all of the existing tests that execute lines in the vicinity of where the source file was changed

About the author

Jim Boone's picture Jim Boone

Jim Boone is a Senior Quality Assurance Analyst at SAS Institute, Inc. Mr. Boone designed, wrote and supported configuration, source code and test management tools for seven years at SAS Institute before moving to Quality Assurance.

In the last five years in QA Mr. Boone has been investigating enhancements to the Coverage Analysis System (CAS) with a focus on testing and using SAS' in-house developed CAS tool set and later finding ways to minimize re-testing using CAS.

Mr. Boone is also the lead test analyst for the SAS Component Language (SCL).

StickyMinds is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

Nov 09
Nov 09
Apr 13
May 03