Abstract
Objectives: From the literature review, it is evident that the concept of “regression testing” inherited in agile software testing originates from software maintenance practices. Therefore, the existing algorithms for regression testing revolve around software maintenance principles rather than agile methodology. This paper aims to evaluate the degree of fitness of the existing regression test-suite development algorithms for performing the regression testing in agile.
Methods: This paper performs a systematic literature review of research work published from 2006 to 2018, which includes a survey of the existing regression testing algorithms to identify and overcome the challenges associated with them while performing regression testing in agile. This paper considers the four research questions into scope for analyzing the suitability of the existing regression test-suite development algorithm for performing regression testing under agile methodology. Further, this paper proposes an approach to develop a suitable regression test-suite for regression testing under agile methodology.
Results: Since four new key challenges were found to be associated with it, the current regression test-suite development algorithm was found unsuitable for performing the regression testing under agile methodology.
Conclusion: The current regression test-suite development algorithms are aligned with software maintenance principles rather than agile methodology. In addition, the newly proposed approach for regression test-suite development was found to be easily adaptable by agile teams as it aligns with agile methodology principles. Finally, for developing a suitable regression test-suite to perform regression testing under agile methodology, this paper recommends adopting the agile principle using the newly proposed approach.
Keywords: Software engineering, software maintenance, agile methodology, regression testing, test-suite, algorithm.
Graphical Abstract
[http://dx.doi.org/10.1002/stv.430]
[http://dx.doi.org/10.1145/2786805.2786878]
[http://dx.doi.org/10.1002/smr.220]
[http://dx.doi.org/10.1002/smr.311]
[http://dx.doi.org/10.1109/ISSRE.2011.29]
[http://dx.doi.org/10.1145/3057269]
[http://dx.doi.org/10.1002/smr.1559]
[http://dx.doi.org/10.1109/ICCIC.2013.6724206]
[http://dx.doi.org/10.1109/IndiaCom.2014.6828189]
[http://dx.doi.org/10.1109/32.962562]
[http://dx.doi.org/10.1109/TSE.2007.38]
[http://dx.doi.org/10.1109/ISSRE.1997.630875]
[http://dx.doi.org/10.1016/j.jss.2006.02.059]
[http://dx.doi.org/10.1002/smr.528]
[http://dx.doi.org/10.1108/IJMPB-06-2016-0054]
[http://dx.doi.org/10.1109/AICAI.2019.8701252]
[http://dx.doi.org/10.1007/978-3-030-00262-6_6]
[http://dx.doi.org/10.1016/j.infsof.2016.09.002]
[http://dx.doi.org/10.1142/S0218194016300013]
[http://dx.doi.org/10.1155/2011/492757]
[http://dx.doi.org/10.1109/CSMR.2013.20]
[http://dx.doi.org/10.1049/iet-sen.2012.0198]
[http://dx.doi.org/10.17706/jsw.10.8.971-990]
[http://dx.doi.org/10.1111/j.1365-2575.2007.00259.x]
[http://dx.doi.org/10.1007/s11219-013-9225-z]
[http://dx.doi.org/10.1007/s11334-015-0262-6]
[http://dx.doi.org/10.14569/IJACSA.2016.070537]
[http://dx.doi.org/10.1007/978-3-319-68837-4_28]
[http://dx.doi.org/10.1109/ICSTW.2011.68]
[http://dx.doi.org/10.1109/ASE.2008.32]
[http://dx.doi.org/10.1145/1027092.1027093]
[http://dx.doi.org/10.1016/j.ijinfomgt.2016.05.025]
[http://dx.doi.org/10.1002/stvr.430]
[http://dx.doi.org/10.1016/j.infsof.2014.04.013]
[http://dx.doi.org/10.1109/ICGEC.2012.124]