Towards automated support for deriving test data from UML statecharts

Cui, Jingfeng

doi:10.22215/etd/2004-05711

Cited by 1 publication

(4 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In this section, we describe those steps at a high level of abstraction, by means of two functions. More detailed algorithms and examples can be found in [31].…”

Section: Building the Invocation Sequence Treementioning

confidence: 99%

“…In the following, we only list example normalization rules due to space constraints. For a complete list the reader is referred to [31].…”

Section: Normalizing Operations On Ocl Typesmentioning

confidence: 99%

“…For the list of all possible changes to model elements, their contract patterns, and the corresponding complementing rules, refer to [31].…”

Section: Complementing Postconditionsmentioning

confidence: 99%

“…A prototype tool called Contract-based Constraint Derivation Tool (CBCDTool) was developed to show the feasibility of our approach towards automated support for deriving test constraints on test data from UML statecharts [28,31]. CBCDTool takes as inputs information on (1) statecharts (including state invariants), and operations contracts, (2) the class diagram (operation signatures, attributes, associations), (3) the TTS, (4) equivalent navigation paths in the class diagram.…”

Section: Prototype Toolmentioning

confidence: 99%

See 3 more Smart Citations

Automated support for deriving test requirements from UML statecharts

2005

View full text Add to dashboard Cite

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.

show abstract

“…In this section, we describe those steps at a high level of abstraction, by means of two functions. More detailed algorithms and examples can be found in [31].…”

Section: Building the Invocation Sequence Treementioning

confidence: 99%

“…In the following, we only list example normalization rules due to space constraints. For a complete list the reader is referred to [31].…”

Section: Normalizing Operations On Ocl Typesmentioning

confidence: 99%

“…For the list of all possible changes to model elements, their contract patterns, and the corresponding complementing rules, refer to [31].…”

Section: Complementing Postconditionsmentioning

confidence: 99%

Section: Prototype Toolmentioning

confidence: 99%

See 2 more Smart Citations