TY - GEN
T1 - History-based test case prioritization for failure information
AU - Cho, Younghwan
AU - Kim, Jeongho
AU - Lee, Eunseok
N1 - Publisher Copyright:
© 2016 IEEE.
PY - 2016/7/2
Y1 - 2016/7/2
N2 - From regression tests, developers seek to determine not only the existence of faults, but also failure information such as what test cases failed. Failure information can assist in identifying suspicious modules or functions in order to fix the detected faults. In continuous integration environments, this can also help managers of the source code repository address unexpected situations caused by regression faults. We introduce an approach, referred to as AFSAC, which is a test case prioritization technique based on history data, that can be used to effectively obtain failure information. Our approach is composed of two stages. First, we statistically analyze the failure history for each test case to order the test cases. Next, we reorder the test cases utilizing the correlation data of test cases acquired by previous test results. We performed an empirical study on two open-source Apache software projects (i.e., Tomcat and Camel) to evaluate our approach. The results of the empirical study show that our approach provides failure information to testers and developers more effectively than other prioritization techniques, and each prioritizing method of our approach improves the ability to obtain failure information.
AB - From regression tests, developers seek to determine not only the existence of faults, but also failure information such as what test cases failed. Failure information can assist in identifying suspicious modules or functions in order to fix the detected faults. In continuous integration environments, this can also help managers of the source code repository address unexpected situations caused by regression faults. We introduce an approach, referred to as AFSAC, which is a test case prioritization technique based on history data, that can be used to effectively obtain failure information. Our approach is composed of two stages. First, we statistically analyze the failure history for each test case to order the test cases. Next, we reorder the test cases utilizing the correlation data of test cases acquired by previous test results. We performed an empirical study on two open-source Apache software projects (i.e., Tomcat and Camel) to evaluate our approach. The results of the empirical study show that our approach provides failure information to testers and developers more effectively than other prioritization techniques, and each prioritizing method of our approach improves the ability to obtain failure information.
KW - Continuous integration environments
KW - Failure information
KW - History data
KW - Regression test
KW - Test case prioritization
UR - https://www.scopus.com/pages/publications/85018510656
U2 - 10.1109/APSEC.2016.066
DO - 10.1109/APSEC.2016.066
M3 - Conference contribution
AN - SCOPUS:85018510656
T3 - Proceedings - Asia-Pacific Software Engineering Conference, APSEC
SP - 385
EP - 388
BT - Proceedings - 23rd Asia-Pacific Software Engineering Conference, APSEC 2016
A2 - Potanin, Alex
A2 - Murphy, Gail C.
A2 - Reeves, Steve
A2 - Dietrich, Jens
PB - IEEE Computer Society
T2 - 23rd Asia-Pacific Software Engineering Conference, APSEC 2016
Y2 - 6 December 2016 through 9 December 2016
ER -