by Yuri Chernak
Testers in the field com­monly deal with incomplete and even missing software requirements. On such projects, they do not have sufficient vis­ibility into the application’s test cover­age. This article provides a solution that I have found to be effective for this problem on many critical projects. The solution, a technique called requirements composition table (RCT), allows testers to assess the regression test suite com­pleteness and identify test coverage gaps. Once gaps are identified, testers can bet­ter decide how to evolve the regression test suite to improve the application’s test coverage.

This article is a re-print from the March, 2008 edition of Better Software magazine.

Yuri Chernak is the president and principal consultant of Valley Forge Consulting, Inc. Yuri has worked for a number of major financial firms in New York leading QA Governance Committees in IT and helping clients improve software requirements and software testing practices. Yuri is a pioneer in implementing for financial applications on Wall Street a new discipline - aspect-oriented requirements engineering. He is a member of the IEEE Computer Society. He has been a speaker at several international conferences in the US and Canada and has published papers in the IEEE publications and other professional journals. Yuri has a doctorate in computer science. Contact him: ychernakyahoo [dot] com

Article Sponsored By