ADBT Frame Work as a Testing Technique: An Improvement in Comparison with Traditional Model Based Testing

Abstract

Abstract-Software testing is an embedded activity in all software development life cycle phases. Due to the difficulties and high costs of software testing, many testing techniques have been developed with the common goal of testing software in the most optimal and cost-effective manner. Model-based testing (MBT) is used to direct testing activities such as test verification and selection. MBT is employed to encapsulate and understand the behavior of the system under test, which supports and helps software engineers to validate the system with various likely actions. The widespread usage of models has influenced the usage of MBT in the testing process, especially with UML. In this research, we proposed an improved model based testing strategy, which involves and uses four different diagrams in the testing process. This paper also discusses and explains the activities in the proposed model with the finite state model (FSM). The comparisons have been done with traditional model based testings in terms of test case generation and result.

Model-based testing using UML activity diagrams: A systematic mapping study

“…These intermediate structures are later used for generating test cases using different graph search methods. In most cases [29,38,58,33,53,40,48,57,43,45,55,62,60], Depth First Search (DFS) has been used for test case generation. However, in some studies [39,41,59,37], DFS has been used in combination with Breath First Search (BFS).…”

“…Graph algorithms [2,29,38,58,33,56,39,72,53,11,40,48,57,41,43,45,55,59,37,62,50,35,52,36,31,47,32,60] 28 [42] proposed a technique to generate all the unique paths in the activity graph (derived from an AD) by covering all the edges and then using a GA to obtain the best test cases. Similarly, Mahali and Acharya [45] proposed an approach to generate all test paths using DFS and then to employ a GA to prioritize them.…”

“…Not specified [32,29,64,50,51,39,52,72,40,48,41,42,36,31,47,45,59,37,60,46] 20 [49] to instrument a Java program according to a given AD. It uses randomly generated test cases to run the instrumented program and gather the corresponding program execution traces.…”

“…In some studies, other UML diagrams such as Use-case, Sequence and Class Diagrams were also employed to complement ADs in the test case generation process. Tiwari and Gupta [59] and Akour et al [60] transformed use-case diagrams into ADs for test case generation. Similarly, Shirole and Kumar [36] proposed an approach to convert sequence diagrams into ADs for test generation.…”

“…Therefore, they cannot be executed in an online fashion. Not specified [30,38,51,72,53,65,11,40,54,44,47,55,66,52,45,49,39,41,29,60,46,42,36] 23…”