2012
DOI: 10.1007/978-3-642-30476-7_2
|View full text |Cite
|
Sign up to set email alerts
|

Using Models of Partial Knowledge to Test Model Transformations

Abstract: Abstract. Testers often use partial knowledge to build test models. This knowledge comes from sources such as requirements, known faults, existing inputs, and execution traces. In Model-Driven Engineering, test inputs are models executed by model transformations. Modelers build them using partial knowledge while meticulously satisfying several well-formedness rules imposed by the modelling language. This manual process is tedious and language constraints can force users to create complex models even for repres… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
21
0

Year Published

2013
2013
2017
2017

Publication Types

Select...
4
4

Relationship

1
7

Authors

Journals

citations
Cited by 19 publications
(21 citation statements)
references
References 24 publications
0
21
0
Order By: Relevance
“…Therefore, in the paper, we use a more permissive instance level formalism called partial snapshots (PS) as an additional input or output of DSL validation where certain language constraints are relaxed. During a typical validation run, such a PS While the underlying formalism of PSs is similar to existing approaches [31,35,50,52], we use them in a novel way to assist the DSL validation process, especially, for constructing validation proofs under specific assumptions. In our workflow, a PS can be generalised from a regular (fully specified) instance model by relaxing specific properties identified by the DSL developer, which can guide efficient validation in practically relevant cases.…”
Section: Partial Snapshotsmentioning
confidence: 99%
See 1 more Smart Citation
“…Therefore, in the paper, we use a more permissive instance level formalism called partial snapshots (PS) as an additional input or output of DSL validation where certain language constraints are relaxed. During a typical validation run, such a PS While the underlying formalism of PSs is similar to existing approaches [31,35,50,52], we use them in a novel way to assist the DSL validation process, especially, for constructing validation proofs under specific assumptions. In our workflow, a PS can be generalised from a regular (fully specified) instance model by relaxing specific properties identified by the DSL developer, which can guide efficient validation in practically relevant cases.…”
Section: Partial Snapshotsmentioning
confidence: 99%
“…Model extensions using partial models The idea of using partial models, which are extended to valid models during verification also appears in [52,31,35]. These initial hints are provided manually to the verification process, while in our approach, these models are assembled from a previous (failed) verification run by adding partial snapshots of the spurious counterexamples or increase the level of approximation.…”
Section: Validation Of Ocl Enriched Metamodelsmentioning
confidence: 99%
“…However, neither of the above approaches proposes a systematic method to repair the transformation in case counter-examples are produced. Sen et al [SMTC12] use Alloy to create complete versions of partially defined models to use for testing model transformations. This process is reminiscent of the way we use Alloy to generate all extensions of the graph rewrite rule, even though the eventual goal is different.…”
Section: Verifying the Transformationsmentioning
confidence: 99%
“…In [20], the generation of input test models must be hand-coded using an imperative language with features for randomly choosing attribute values and association ends. Input models are also hand-crafted in [43], although they are only required to conform to a relaxed version of the input meta-model without mandatory references and general constraints. These so-called partial models are transformed into Alloy and fed into a constraint solver to find valid instances of the original meta-model which can be used for testing.…”
Section: State Of the Artmentioning
confidence: 99%
“…Coverage criteria. Existing black-box testing approaches for model transformations either do not consider coverage criteria [20,43], or support input meta-model coverage (partitioning of attribute values, number of classes and associations, etc.) [13,14,42].…”
Section: State Of the Artmentioning
confidence: 99%