Links for fulltext
(May Require Subscription)
- Publisher Website: 10.1016/j.infsof.2012.01.006
- Scopus: eid_2-s2.0-84862821558
- WOS: WOS:000304387600006
- Find via
Supplementary
- Citations:
- Appears in Collections:
Article: How well does test case prioritization integrate with statistical fault localization?
Title | How well does test case prioritization integrate with statistical fault localization? | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Authors | |||||||||||||
Keywords | Adaptive random testing Continuous integration Coverage Software process integration Statistical fault localization Test case prioritization | ||||||||||||
Issue Date | 2012 | ||||||||||||
Publisher | Elsevier BV. The Journal's web site is located at http://www.elsevier.com/locate/infsof | ||||||||||||
Citation | Information And Software Technology, 2012, v. 54 n. 7, p. 739-758 How to Cite? | ||||||||||||
Abstract | Context: Effective test case prioritization shortens the time to detect failures, and yet the use of fewer test cases may compromise the effectiveness of subsequent fault localization. Objective: The paper aims at finding whether several previously identified effectiveness factors of test case prioritization techniques, namely strategy, coverage granularity, and time cost, have observable consequences on the effectiveness of statistical fault localization techniques. Method: This paper uses a controlled experiment to examine these factors. The experiment includes 16 test case prioritization techniques and four statistical fault localization techniques using the Siemens suite of programs as well as grep, gzip, sed, and flex as subjects. The experiment studies the effects of the percentage of code examined to locate faults from these benchmark subjects after a given number of failures have been observed. Results: We find that if testers have a budgetary concern on the number of test cases for regression testing, the use of test case prioritization can save up to 40% of test case executions for commit builds without significantly affecting the effectiveness of fault localization. A statistical fault localization technique using a smaller fraction of a prioritized test suite is found to compromise its effectiveness seriously. Despite the presence of some variations, the inclusion of more failed test cases will generally improve the fault localization effectiveness during the integration process. Interestingly, during the variation periods, adding more failed test cases actually deteriorates the fault localization effectiveness. In terms of strategies, Random is found to be the most effective, followed by the ART and Additional strategies, while the Total strategy is the least effective. We do not observe sufficient empirical evidence to conclude that using different coverage granularity levels have different overall effects. Conclusion: The paper empirically identifies that strategy and time-cost of test case prioritization techniques are key factors affecting the effectiveness of statistical fault localization, while coverage granularity is not a significant factor. It also identifies a mid-range deterioration in fault localization effectiveness when adding more test cases to facilitate debugging. © 2012 Elsevier B.V. All rights reserved. | ||||||||||||
Persistent Identifier | http://hdl.handle.net/10722/147019 | ||||||||||||
ISSN | 2023 Impact Factor: 3.8 2023 SCImago Journal Rankings: 1.320 | ||||||||||||
ISI Accession Number ID |
Funding Information: This research is supported in part by a grant of the Basic Research Fund of Beihang University, a grant of the Natural Science Foundation of China (Project No. 61003027), a strategy research grant of City University of Hong Kong (Project No. 7002673), a grant of the General Research Fund of the Research Grants Council of Hong Kong (Project No. 717308), and a discovery grant of the Australian Research Council (Project No. DP120104773). | ||||||||||||
References |
DC Field | Value | Language |
---|---|---|
dc.contributor.author | Jiang, B | en_HK |
dc.contributor.author | Zhang, Z | en_HK |
dc.contributor.author | Chan, WK | en_HK |
dc.contributor.author | Tse, TH | en_HK |
dc.contributor.author | Chen, TY | en_HK |
dc.date.accessioned | 2012-05-23T05:53:39Z | - |
dc.date.available | 2012-05-23T05:53:39Z | - |
dc.date.issued | 2012 | en_HK |
dc.identifier.citation | Information And Software Technology, 2012, v. 54 n. 7, p. 739-758 | en_HK |
dc.identifier.issn | 0950-5849 | en_HK |
dc.identifier.uri | http://hdl.handle.net/10722/147019 | - |
dc.description.abstract | Context: Effective test case prioritization shortens the time to detect failures, and yet the use of fewer test cases may compromise the effectiveness of subsequent fault localization. Objective: The paper aims at finding whether several previously identified effectiveness factors of test case prioritization techniques, namely strategy, coverage granularity, and time cost, have observable consequences on the effectiveness of statistical fault localization techniques. Method: This paper uses a controlled experiment to examine these factors. The experiment includes 16 test case prioritization techniques and four statistical fault localization techniques using the Siemens suite of programs as well as grep, gzip, sed, and flex as subjects. The experiment studies the effects of the percentage of code examined to locate faults from these benchmark subjects after a given number of failures have been observed. Results: We find that if testers have a budgetary concern on the number of test cases for regression testing, the use of test case prioritization can save up to 40% of test case executions for commit builds without significantly affecting the effectiveness of fault localization. A statistical fault localization technique using a smaller fraction of a prioritized test suite is found to compromise its effectiveness seriously. Despite the presence of some variations, the inclusion of more failed test cases will generally improve the fault localization effectiveness during the integration process. Interestingly, during the variation periods, adding more failed test cases actually deteriorates the fault localization effectiveness. In terms of strategies, Random is found to be the most effective, followed by the ART and Additional strategies, while the Total strategy is the least effective. We do not observe sufficient empirical evidence to conclude that using different coverage granularity levels have different overall effects. Conclusion: The paper empirically identifies that strategy and time-cost of test case prioritization techniques are key factors affecting the effectiveness of statistical fault localization, while coverage granularity is not a significant factor. It also identifies a mid-range deterioration in fault localization effectiveness when adding more test cases to facilitate debugging. © 2012 Elsevier B.V. All rights reserved. | en_HK |
dc.language | eng | en_US |
dc.publisher | Elsevier BV. The Journal's web site is located at http://www.elsevier.com/locate/infsof | en_HK |
dc.relation.ispartof | Information and Software Technology | en_HK |
dc.rights | NOTICE: this is the author’s version of a work that was accepted for publication in Information and Software Technology. Changes resulting from the publishing process, such as peer review, editing, corrections, structural formatting, and other quality control mechanisms may not be reflected in this document. Changes may have been made to this work since it was submitted for publication. A definitive version was subsequently published in Information and Software Technology, 2012, v. 54 n. 7, p. 739-758. DOI: 10.1016/j.infsof.2012.01.006 | - |
dc.rights | This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. | - |
dc.subject | Adaptive random testing | en_HK |
dc.subject | Continuous integration | en_HK |
dc.subject | Coverage | en_HK |
dc.subject | Software process integration | en_HK |
dc.subject | Statistical fault localization | en_HK |
dc.subject | Test case prioritization | en_HK |
dc.title | How well does test case prioritization integrate with statistical fault localization? | en_HK |
dc.type | Article | en_HK |
dc.identifier.email | Tse, TH: thtse@cs.hku.hk | en_HK |
dc.identifier.authority | Tse, TH=rp00546 | en_HK |
dc.description.nature | postprint | - |
dc.identifier.doi | 10.1016/j.infsof.2012.01.006 | en_HK |
dc.identifier.scopus | eid_2-s2.0-84862821558 | en_HK |
dc.identifier.hkuros | 199409 | en_US |
dc.relation.references | http://www.scopus.com/mlt/select.url?eid=2-s2.0-84862821558&selection=ref&src=s&origin=recordpage | en_HK |
dc.identifier.volume | 54 | en_HK |
dc.identifier.issue | 7 | en_HK |
dc.identifier.spage | 739 | en_HK |
dc.identifier.epage | 758 | en_HK |
dc.identifier.isi | WOS:000304387600006 | - |
dc.publisher.place | Netherlands | en_HK |
dc.identifier.scopusauthorid | Jiang, B=35199818000 | en_HK |
dc.identifier.scopusauthorid | Zhang, Z=36198974100 | en_HK |
dc.identifier.scopusauthorid | Chan, WK=23967779900 | en_HK |
dc.identifier.scopusauthorid | Tse, TH=54971059300 | en_HK |
dc.identifier.scopusauthorid | Chen, TY=35247605500 | en_HK |
dc.identifier.citeulike | 10367104 | - |
dc.identifier.issnl | 0950-5849 | - |