ACM Home Page
Please provide us with feedback. Feedback
Regression test selection on system requirements
Full text PdfPdf (522 KB)
Source
India Software Engineering Conference archive
Proceedings of the 1st conference on India software engineering conference table of contents
Hyderabad, India
SESSION: Testing table of contents
Pages 87-96  
Year of Publication: 2008
ISBN:978-1-59593-917-3
Authors
Pavan Kumar Chittimalli  Tata Consultancy Services Ltd., Atlanta, GA
Mary Jean Harrold  Georgia Institute of Technology, Atlanta, GA
Sponsors
ACM: Association for Computing Machinery
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 14,   Downloads (12 Months): 135,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1342211.1342229
What is a DOI?

ABSTRACT

Regression testing, which is performed after changes are made to a software system, can be used before release of new versions of the system. However, practitioners often have little time to perform this regression testing because of the quick-release cycles of such modified systems. Thus, they may use a random-testing approach or perform little regression testing. This lack of adequate regression testing can cause bugs in untested parts of the program to be exposed only during production or field usage. To improve the efficiency of the regression testing, and thus enable its use before release, techniques that select and run only those test cases that are related to the changes or prioritize the test cases based on criticality or perceived effectiveness have been presented. These technique typically use some representation of the software such as a system model or the source code to perform the test selection and prioritization. However, in practice, access to a system modelor the source code may not be possible. To provide regression test selection in practice, we have developed, and present in this paper, a novel approach to regression test selection that, instead of using a system model or the source code, uses the system requirements and their associated test cases, which are typically available to developers/testers. The approach uses the set of system requirements, usually in natural language or some informal notation, that represent what is to be tested about the system. The technique uses these requirements, along with the set of test cases and their criticality that are associated with the requirements, to select test cases for use in regression testing. In this paper, we also present a case study that shows the potential effectiveness of our technique


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Tata Consultancy Services Limited. http://www.tcs.com/AboutUs/AboutUs.html.
2
 
3
 
4
 
5
P. K. Chittimalli, M. Bapat, and R. D. Naik. ProAX: A program analysis and transformation framework. In TCS Technical Architect's Conference (TACTiCS 2004), Hyderabad, December 2004.
 
6
P. K. Chittimalli and M. J. Harrold. Re-computing coverage information to assist regression testing. In International Conference on Software Maintenance (ICSM 2007), pages 164--173, October 2007.
 
7
D. Kung, J. Gao, P. Hsia, Y. Toyashima, and C. Chen. Firewall regression testing and software maintenance of object-oriented systems. 1994.
 
8
H. K. N. Leung and L. J. White. Insights into regression testing. In Proceedings of the Conference on Software Maintenance -- 1989, pages 60--69, 1989.
9
10
 
11
 
12
G. Rothermel, R. Untch, C. Chu, and M. J. Harrold. Test case prioritization. In Technical Report GIT-99-28, College of Computing, Georgia Institute of Technology (GIT-99-28 1999), Georgia Institute of Technology, December 1999.
 
13
 
14

Collaborative Colleagues:
Pavan Kumar Chittimalli: colleagues
Mary Jean Harrold: colleagues