A Graph Transformation Approach for Automatic Test Cases Generation from UML Activity Diagrams

Hettab, Abdelkamel; Kerkouche, Elhillali; Chaoui, Allaoua

doi:10.1145/2790798.2790801

Cited by 11 publications

(24 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…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).…”

Section: Test Case Generation Methods (Rq5)mentioning

confidence: 99%

“…One of the main benefits of transforming an AD into an activity graph is that one can use several well-established graph-search algorithms for generating test cases with respect to given graph-based coverage criteria. However, Hettab et al [38] claimed that the activity graphs do not encapsulate all the features of an AD which are necessary for test generation and proposed an Extended Activity Dependency Graph (EADG). A vertex in an EADG can represent a set of nodes in the AD, instead of a single node, implying that the nodes inside the vertex are concurrent and they can be executed simultaneously.…”

Section: Modeling Notations (Rq2)mentioning

confidence: 99%

“…However, 35 % (15) of the studies use a combination of several coverage criteria as shown in Table 7. Continued on next page [49] Simple path, activity/state/node, transition/edge Chen et al [65] Key path, interaction, activity/node/edge Vieira et al [64] Happy path, data Hettab et al [38] Basic path for non-concurrent activities, simple path for concurrent activities Yuan et al [58] Activity/state/node, transition/edge Sapna et al [50] Simple and all paths, activity/state/node, transition/edge Farooq et al [66] Interleaving node/edge, transition/edge, branch Samuel and Mall [35] All dependency path, predicate, boundary testing Fan et al [72] Activity/state/node, transition/edge, join and fork, branch Sapna et al [53] Key path, activity/state/node, transition/edge Boghdady et. at.…”

Section: Model Validation and Verification (Rq3)mentioning

confidence: 99%

See 2 more Smart Citations

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

Ahmad

Iqbal

Ashraf

et al. 2019

Computer Science Review

View full text Add to dashboard Cite

Context:The Unified Modeling Language (UML) has become the de facto standard for software modeling. UML models are often used to visualize, understand, and communicate the structure and behavior of a system. UML activity diagrams (ADs) are often used to elaborate and visualize individual use cases. Due to their higher level of abstraction and process-oriented perspective, UML ADs are also highly suitable for model-based test generation. In the last two decades, different researchers have used UML ADs for test generation. Despite the growing use of UML ADs for model-based testing, there are currently no comprehensive and unbiased studies on the topic. Objective: To present a comprehensive and unbiased overview of the state-of-the-art on model-based testing using UML ADs. Method: We review and structure the current body of knowledge on model-based testing using UML ADs by performing a systematic mapping study using well-known guidelines. We pose nine research questions, outline our selection criteria, and develop a classification scheme. Results: The results comprise 41 primary studies analyzed against nine research questions. We also highlight the current trends and research gaps in model-based testing using UML ADs and discuss some shortcomings for researchers and practitioners working in this area. The results show that the existing approaches on model-based testing using UML ADs tend to rely on intermediate formats and formalisms for model verification and test generation, employ a multitude of graph-based coverage criteria, and use graph search algorithms. Conclusion: We present a comprehensive overview of the existing approaches on model-based testing using UML ADs. We conclude that (1) UML ADs are not being used for non-functional testing, (2) only a few approaches have been validated against realistic, industrial case studies, (3) most approaches target very restricted application domains, and (4) there is currently a clear lack of holistic approaches for model-based testing using UML ADs.

show abstract

Section: Test Case Generation Methods (Rq5)mentioning

confidence: 99%

Section: Modeling Notations (Rq2)mentioning

confidence: 99%

Section: Model Validation and Verification (Rq3)mentioning

confidence: 99%

See 1 more Smart Citation

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

Ahmad

Iqbal

Ashraf

et al. 2019

Computer Science Review

View full text Add to dashboard Cite

show abstract

“…Various approaches to MBTCC employ SCs or sequence diagrams as input models . Furthermore, other concepts employing ADs as input models for MBTCC do not support concurrency at all . Besides the target on the language usage, other approaches presented different tools to support and to facilitate MBT, which include, for instance, the tool MBTsuite .…”

Section: Related Workmentioning

confidence: 99%

“…[37][38][39] Furthermore, other concepts employing ADs as input models for MBTCC do not support concurrency at all. [40][41][42] Besides the target on the language usage, other approaches presented different tools to support and to facilitate MBT, which include, for instance, the tool MBTsuite. 54 It employs ADs for test case creation and it is capable of exporting these ADs into a variety of different outputs.…”

Section: Related Workmentioning

confidence: 99%

SMArDT modeling for automotive software testing

et al. 2018

View full text Add to dashboard Cite

Summary Efficient testing is a crucial prerequisite to engineer reliable automotive software successfully. However, manually deriving test cases from ambiguous textual requirements is costly and error‐prone. Model‐based software engineering captures requirements in structured, comprehensible, and formal models, which enables early consistency checking and verification. Moreover, these models serve as an indispensable basis for automated test case derivation. To facilitate automated test case derivation for automotive software engineering, we conducted a survey with testing experts of the BMW Group and conceived a method to extend the BMW Group's specification method for requirements, design, and test methodology by model‐based test case derivation. Our method is realized for a variant of systems modeling language activity diagrams tailored toward testing automotive software and a model transformation to derive executable test cases. Hereby, we can address many of the surveyed practitioners' challenges and ultimately facilitate quality assurance for automotive software.

show abstract

Agent-Based Regression Test Case Generation using Class Diagram, Use cases and Activity Diagram

Arora

Bhatia

2018

Procedia Computer Science

View full text Add to dashboard Cite

A Graph Transformation Approach for Automatic Test Cases Generation from UML Activity Diagrams

Cited by 11 publications

References 5 publications

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

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

SMArDT modeling for automotive software testing

Agent-Based Regression Test Case Generation using Class Diagram, Use cases and Activity Diagram

Contact Info

Product

Resources

About