Automated support for deriving test requirements from UML statecharts.

Saved in:

Bibliographic Details
Title:	Automated support for deriving test requirements from UML statecharts.
Authors:	Briand, L. C.¹ briand@sce.carleton.ca, Labiche, Y.¹ labiche@sce.carleton.ca, Cui, J.¹ jfcui@sce.carleton.ca
Source:	Software & Systems Modeling. Nov2005, Vol. 4 Issue 4, p399-423. 25p.
Subjects:	Statecharts (Computer science), Structured techniques of electronic data processing, Software engineering, Automation, Industrial engineering
Abstract:	Many statechart-based testing strategies result in specifying a set of paths to be executed through a (flattened) statechart. These techniques can usually be easily automated so that the tester does not have to go through the tedious procedure of deriving paths manually to comply with a coverage criterion. The next step is then to take each test path individually and derive test requirements leading to fully specified test cases. This requires that we determine the system state required for each event/transition that is part of the path to be tested and the input parameter values for all events and actions associated with the transitions. We propose here a methodology towards the automation of this procedure, which is based on a careful normalization and analysis of operation contracts and transition guards written with the Object Constraint Language (OCL). It is illustrated by one case study that exemplifies the steps of our methodology and provides a first evaluation of its applicability. [ABSTRACT FROM AUTHOR]
	Copyright of Software & Systems Modeling is the property of Springer Nature and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)
Database:	Engineering Source

Description
Abstract:	Many statechart-based testing strategies result in specifying a set of paths to be executed through a (flattened) statechart. These techniques can usually be easily automated so that the tester does not have to go through the tedious procedure of deriving paths manually to comply with a coverage criterion. The next step is then to take each test path individually and derive test requirements leading to fully specified test cases. This requires that we determine the system state required for each event/transition that is part of the path to be tested and the input parameter values for all events and actions associated with the transitions. We propose here a methodology towards the automation of this procedure, which is based on a careful normalization and analysis of operation contracts and transition guards written with the Object Constraint Language (OCL). It is illustrated by one case study that exemplifies the steps of our methodology and provides a first evaluation of its applicability. [ABSTRACT FROM AUTHOR]
ISSN:	16191366
DOI:	10.1007/s10270-005-0090-5