Abstract
The average percent of faults detected (APFD) and its variant versions are widely used to evaluate prioritized test suite’s efficiency. However, APFD is only available for classic test case prioritization, where all prioritized test suites under comparison contain the same number of test cases. If people overlook this phenomenon, they may obtain incorrect results in some non-classic scenarios, where prioritized test suites have different sizes. In addition, it can’t precisely illustrate the process of fault detection. Besides the APFD, most of its variants have similar problems. This paper points out these limitations in detail, by analyzing the physical explanation of APFD series metrics. To avoid limitations, a series of metrics including RAPFD, RAPFDC , RAPFDW and RAPFDCW are proposed for different types of scenarios. All proposed metrics refer to both the speed of fault detection and the constraint of testing resource. There is an example in this paper showing that proposed metrics provide much more precise illustrations of fault detection process and fault detection efficiency of test suite. Keywords—software testing, test case prioritization, fault detection efficiency, metric
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
