A survey on Test Suite Reduction frameworks and tools

Abstract

Abstract-Software testing is a widely accepted practice that ensures the quality of a System under Test (SUT). However, the gradual increase of the test suite size demands high portion of testing budget and time. Test Suite Reduction (TSR) is considered a potential approach to deal with the test suite size problem. Moreover, a complete automation support is highly recommended for software testing to adequately meet the challenges of a resource constrained testing environment. Several TSR frameworks and tools have been proposed to efficiently address the test-suite size problem. The main objective of the paper is to comprehensively review the state-of-the-art TSR frameworks to highlights their strengths and weaknesses. Furthermore, the paper focuses on devising a detailed thematic taxonomy to classify existing literature that helps in understanding the underlying issues and proof of concept. Moreover, the paper investigates critical aspects and related features of TSR frameworks and tools based on a set of defined parameters. We also rigorously elaborated various testing domains and approaches followed by the extant TSR frameworks. The results reveal that majority of TSR frameworks focused on randomized unit testing, and a considerable number of frameworks lacks in supporting multi-objective optimization problems. Moreover, there is no generalized framework, effective for testing applications developed in any programming domain. Conversely, Integer Linear Programming (ILP) based TSR frameworks provide an optimal solution for multi-objective optimization problems and improve execution time by running multiple ILP in parallel. The study concludes with new insights and provides an unbiased view of the state-of-the-art TSR frameworks. Finally, we present potential research issues for further investigation to anticipate efficient TSR frameworks.

A Multi Criteria based Test Suite Optimization Framework

“…So, the primary objective behind optimization process is to find out the representative test set which has a minimal number of test cases that covers the whole program and find the same number of faults as original test suite did. A complete survey of the different techniques and critical investigation on different tools used for test suite optimization can be found in the research work by Yoo and Harman [6] and Khan et al [7]. After study we found that using only single criteria we cannot improve the optimization process effectively [12].…”

Detecting Java software similarities by using different clustering techniques

“…In the context of software engineering, clustering has been used in the past, for reverse engineering and software maintenance tasks, with the aim to categorise software artifacts [22,23]. The concept of similarity is a fundamental building block for any clustering technique, as well as a key issue in various contexts, such as detecting cloned code [24,25,26,27], software plagiarism [28], or reducing test suite size in modelbased testing [29,30]. According to Walenstein et al [31], a workable common understanding for software similarity is as follows: "the degree to which two distinct programs are similar is related to how precisely they are alike."…”

ContextDrive: Towards a Functional Scenario-Based Testing Framework for Context-Aware Applications

“…Software testing is a widely used practice and is carried out to ensure the quality of software being developed and to ensure that the software is defect free. The Software testing process includes a number of phases such as test planning, test definition, test suite reduction [1], defect tracking and test closure activities [2]. While the test case execution phase is usually recursive and requires considerable testing time, cost and efforts.…”