Model driven automatic unit testing technology tool architecture

The approach towards system engineering according to Model-Driven Architectures (MDA) with code generation derived from model implies also an increased need for research on automation of the test generation process. This paper presents an approach to derive executable tests from UML 2.0 Testing Profile diagrams automatically. In particular, an approach to derive executable tests within the Testing and Test Control Notation (TTCN-3) is discussed. The transformation rules between the source U2TP meta-model to the target TTCN-3 meta-model are given.

Conference On Computer Aided Systems Theory, 2003

Executable graphical models are used throughout the model-based development process for embedded controls. The test process accompanying model-based development can profit from the existence of such executable models in various ways. For instance, in addition to traditional code coverage analysis the executable model can also be subjected to structural coverage metrics on model level. This paper gives the details and results of our experience with the deployment of model coverage metrics and the application of test vector generators and coverage analyzers.

Lecture Notes in Computer Science

2004

The Unified Modeling Language (UML) is gaining wide acceptance in industry and we, at Siemens Corporate Research, are seeking ways in which UML diagrams can be used as the basis for functional testing. Our approach focuses on developing effective techniques and tools for test case generation and coupling them with suitable execution tools for unit, integration and system testing. For example, our current approaches focus on integrating our techniques with the Rational Rose UML modeling tool and unit test execution tools such as Junit and system test tools, that is, capture-replay tools such as Compuware Testpartner. The goal of our approach is to generate a set of black-box conformance tests that can be used to validate a component, subsystem or application under test.

2007

This paper describes a systematic review performed on modelbased testing (MBT) approaches. A selection criterion was used to narrow the initially identified four hundred and six papers to focus on seventy-eight papers. Detailed analysis of these papers shows where MBT approaches have been applied, the characteristics, and the limitations. The comparison criteria includes representation models, support tools, test coverage criteria, the level of automation, intermediate models, and the complexity. This paper defines and explains the review methodology and presents some results.

Electronic Notes in Theoretical Computer Science, 2007

Model-based testing has been proposed as a technique to automatically verify that a system conforms to its specification. A popular approach is to use a model-checker to produce a set of test cases by formulating the test generation problem as a reachability problem. To guide the selection of test cases, a coverage criterion is often used. A coverage criterion can be seen as a set of items to be covered, called coverage items. We propose an on-the-fly algorithm that generates a test suite that covers all feasible coverage items. The algorithm returns a set of traces that includes a path fulfilling each item, without including redundant paths. The reachability algorithm explores a state only if it might increase the total coverage. The decision is global in the sense that it does not only regard each individual local search branch in isolation, but the total coverage in all branches together. For simpler coverage criteria as location of edge coverage, this implies that each model state is never explored twice. The algorithm presented in this paper has been implemented in the test generation tool UPPAAL CO ER. We present encouraging results from applying the tool to a set of experiments and in an industrial sized case study.

Präsentation auf der TAV21 in …, 2004

The Unified Modeling Language (UML) is gaining wide acceptance in industry and we, at Siemens Corporate Research, are seeking ways in which UML diagrams can be used as the basis for functional testing. Our approach focuses on developing effective techniques and tools for test case generation and coupling them with suitable execution tools for unit, integration and system testing. For example, our current approaches focus on integrating our techniques with the Rational Rose UML modeling tool and unit test execution tools such as Junit and system test tools, that is, capture-replay tools such as Compuware Testpartner. The goal of our approach is to generate a set of black-box conformance tests that can be used to validate a component, subsystem or application under test.

Software and Systems Modeling, 2002

This article describes an approach for automatically generating and executing system tests, which can be used to improve the validation of an application. Tests are automatically generated from behavioural models of the application using the unified modelling language (UML) and then executed using a suitable test execution environment. For this paper, we demonstrate our approach by means of an application that interacts with its users via a graphical user interface. Thus, we discuss the test-execution phase with respect to a commercial user interface (UI) or capture-replay tool. In this article, we show how, in the first step, a test designer manually annotates the UML models, which may have been semiautomatically extracted from existing, textual-use case documentation, with test requirements. In the second step, the test-generation tool automatically creates a set of textual test procedures (test cases) or executable test scripts. In the third step, a test executor runs these against the system under test using a commercial UI testing tool. The goal of the article is to illustrate the benefits of an automated, model-based approach for improving system test design, generation and execution. Details regarding the different tools are given.

2005

Model centric development and engineering according to Model-Driven Architectures (MDA) has recently gained much attention. This paper presents an approach how a model centric approach cannot only b e used for system development but also at the same time to support the provision of system tests which are to be an integral part of the overall system development. The paper discusses the various artefacts for model-based testing along MDA and their relation to the artefacts in system development. The testing artefacts can be designed and modelled with the UML 2.0 Testing Profile (U2TP) which extends UML 2.0 with test specific concepts.

This paper presents an architecture for model-based testing using a profile of the Unified Modeling Language (UML). Class, object, and state diagrams are used to define essential models: descriptions that characterise the entire range of possible behaviours, in terms of the actions and events of the model. Object and state diagrams are used to introduce test directives.