@ist_spl

Automation of GUI testing using a model-driven approach

, , , , and . AST '06: Proceedings of the 2006 international workshop on Automation of software test, page 9--14. New York, NY, USA, ACM, (2006)
DOI: http://doi.acm.org/10.1145/1138929.1138932

Abstract

This paper describes an ongoing research on test case generation based on Unified Modeling Language (UML). The described approach builds on and combines existing techniques for data and graph coverage. It first uses the Category-Partition method to introduce data into the UML model. UML Use Cases and Activity diagrams are used to respectively describe which functionalities should be tested and how to test them. This combination has the potential to create a very large number of test cases. This approach offers two ways to manage the number of tests. First, custom annotations and guards use the Category-Partition data which allows the designer tight control over possible, or impossible, paths. Second, automation allows different configurations for both the data and the graph coverage. The process of modeling UML activity diagrams, annotating them with test data requirements, and generating test scripts from the models is described. The goal of this paper is to illustrate the benefits of our model-based approach for improving automation on software testing. The approach is demonstrated and evaluated based on use cases developed for testing a graphical user interface (GUI).

Description

MR: UML-Use-Cases werden mit Aktivitaetsdiagrammen beschrieben, an denen Aktivitaets-Annotationen mit der Verwendung von Testdaten angebracht werden. Die Testdaten werden nach der Category-Partition-Methode von Entwicklern angebracht. Zusätzlich sind die Aktivitaetsdiagramme um Guard-Conditions erweitert (es sind Constraints an den Pfeilen von Verzweigungen angebracht in einer speziellen TSL Sprache). Anwendung verschiedener Testauswahlkriterien gezeigt. Technik für den Systemtest angedacht, an einem GUI-Test als Beispiel gezeigt. Nachteil: Ansatz schweigt in Bezug auf Testorakel. Nur im 'Future work'-Abschnitt wurde angemerkt: "We are investigating ways to improve the test cases with detailed verification points and arbiters.". IST-SPL: wertvoll.

Links and resources

Tags