ACM Home Page
Please provide us with feedback. Feedback
Finding failure-inducing changes in java programs using change classification
Full text PdfPdf (275 KB)
Source Foundations of Software Engineering archive
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering table of contents
Portland, Oregon, USA
SESSION: Mining failures and bugs table of contents
Pages: 57 - 68  
Year of Publication: 2006
ISBN:1-59593-468-5
Authors
Maximilian Stoerzer  University of Passau, Passau, Germany
Barbara G. Ryder  Rutgers University, Piscataway, NJ
Xiaoxia Ren  Rutgers University, Piscataway, NJ
Frank Tip  IBM T.J. Watson Research Center, Yorktown Heights, NY
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 9,   Downloads (12 Months): 79,   Citation Count: 8
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

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

ABSTRACT

Testing and code editing are interleaved activities during program development. When tests fail unexpectedly, the changes that caused the failure(s) are not always easy to find. We explore how change classification can focus programmer attention on failure-inducing changes by automatically labeling changes Red, Yellow, or Green, indicating the likelihood that they have contributed to a test failure. We implemented our change classification tool JUnit/CIA as an ex-tension to the JUnit component within Eclipse, and evaluated its effectiveness in two case studies. Our results indicate that change classification is an effective technique for finding failure-inducing changes.


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
 
2
BOHNER, S.A., AND ARNOLD, R. S. An introduction to software change impact analysis. In Software Change Impact Analysis, S. A. Bohner and R. S. Arnold, Eds. IEEE Computer Society Press, 1996, pp. 1--26.
 
3
4
5
 
6
DALLMEIER,V.,LINDIG, C., AND ZELLER, A. Lightweight defect localization for Java. In Proc. 19th European Conf. on Object- Oriented Programming (ECOOP'05) (Glasgow, Scotland, 2005).
7
 
8
9
10
11
12
13
 
14
 
15
 
16
17
18
19
 
20
LYLE, J., AND WEISER, M. Automatic bug location by program slicing. In Proceedings of the Second International Conference on Computers and Applications (Beijing (Peking), China, 1987), pp. 877--883.
21
 
22
 
23
REN, X., CHESLEY, O., AND RYDER, B. G. Crisp: A debugging tool for Java programs. IEEE Transactions on Software Engineering (April 2006). In press.
24
 
25
RENIERIS, M., AND REISS, S. Fault localization with nearest neighbor queries. In In Proceedings of the 18th IEEE International Conference on Automated Software Engineering (Montreal, Quebec, Canada, October 2003), pp. 30--39.
26
27
28
 
29
30
31
 
32
STOERZER, M., RYDER, B. G., REN, X., AND TIP, F. Finding failure-inducing changes using change classification. Tech. Rep. DCS-TR-582, Rutgers University Department of Computer Science, September 2005.
 
33
TIP, F. A survey of program slicing techniques. J. of Programming Languages 3, 3 (1995), 121--189.
34
 
35
TONELLA, P. Using a concept lattice of decomposition slices for program understanding and impact analysis. IEEE Trans. on Softw. Engineering 29,6 (2003), 495--509.
 
36
 
37
38
39
40
 
41

CITED BY  8

Collaborative Colleagues:
Maximilian Stoerzer: colleagues
Barbara G. Ryder: colleagues
Xiaoxia Ren: colleagues
Frank Tip: colleagues