This Article 
   
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Tool Support for Change-Centric Test Development
May/June 2010 (vol. 27 no. 3)
pp. 66-71
ASCII Text
x 
 
Jan Wloka, Einar Hoest, Barbara G. Ryder, "Tool Support for Change-Centric Test Development," IEEE Software, vol. 27, no. 3, pp. 66-71, May/June, 2010.
 
 
BibTex
x
 
@article{ 10.1109/MS.2009.159,
author = {Jan Wloka and Einar Hoest and Barbara G. Ryder},
title = {Tool Support for Change-Centric Test Development},
journal ={IEEE Software},
volume = {27},
number = {3},
issn = {0740-7459},
year = {2010},
pages = {66-71},
doi = {http://doi.ieeecomputersociety.org/10.1109/MS.2009.159},
publisher = {IEEE Computer Society},
address = {Los Alamitos, CA, USA},
}
 
 
RefWorks Procite/RefMan/Endnote
x 
 
TY - MGZN
JO - IEEE Software
TI - Tool Support for Change-Centric Test Development
IS - 3
SN - 0740-7459
SP66
EP71
EPD - 66-71
A1 - Jan Wloka,
A1 - Einar Hoest,
A1 - Barbara G. Ryder,
PY - 2010
KW - Unit testing
KW - test-driven development
KW - test coverage
KW - change impact analysis
VL - 27
JA - IEEE Software
ER -
 
Jan Wloka, Rutgers University, New Brunswick
Einar Hoest, Norwegian Computing Center, Oslo
Barbara G. Ryder, Virginia Tech, Blacksburg
Current development tools for unit testing help automate test execution, report results, and generate test stubs, but they offer no aid in designing tests aimed specifically at the effects of changes to a program. This article describes a method for applying change impact analysis to test-driven development, thereby providing developers with quantitative feedback from test coverage on their changes. They can then use this information to meet defined coverage goals or to help generate new tests to reveal unanticipated change effects. The authors' approach, called change-centric test development, is tool supported; a typical scenario shows the effectiveness of their tool JUnitMX in a practical feasibility study.

1. L. Copeland, A Practitioner's Guide to Software Test Design, Artech House, 2004.
2. K. Beck, "Aim, Fire," IEEE Software, vol. 18, no. 5, 2001, pp. 87–89.
3. M. Fowler et al., Refactoring: Improving the Design of Existing Code, Addison-Wesley, 1999.
4. P. McBreen, Questioning Extreme Programming, Addison-Wesley Professional, 2002.
5. X. Ren et al., "Chianti: A Tool for Practical Change Impact Analysis of Java Programs," Proc. ACM SIGPLAN Conf. Object-Oriented Programming, Systems and Applications (OOPSLA), ACM Press, 2004, pp. 432–448.
6. B.G. Ryder and F. Tip, "Change Impact Analysis for Object-Oriented Programs," Proc. 2001 ACM SIGPLAN-SIGSOFT Workshop on Program Analysis for Software Tools and Engineering, ACM Press, 2001, pp. 46–53.
7. R. Arnold and S. Bohner, Software Change Impact Analysis, Wiley-IEEE CS Press, 1996.
8. X. Ren, O. Chesley, and B.G. Ryder, "Crisp, A Debugging Tool for Java Programs," IEEE Trans. Software Eng., vol. 32, no. 9, 2006, pp. 1–16.

Index Terms:
Unit testing, test-driven development, test coverage, change impact analysis
Citation:
Jan Wloka, Einar Hoest, Barbara G. Ryder, "Tool Support for Change-Centric Test Development," IEEE Software, vol. 27, no. 3, pp. 66-71, May-June 2010, doi:10.1109/MS.2009.159
Usage of this product signifies your acceptance of the Terms of Use.