2017
DOI: 10.1007/s10270-017-0620-y
|View full text |Cite
|
Sign up to set email alerts
|

From use case maps to executable test procedures: a scenario-based approach

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
3
3
1

Relationship

1
6

Authors

Journals

citations
Cited by 9 publications
(9 citation statements)
references
References 19 publications
0
9
0
Order By: Relevance
“…Kesserwan et al [78] provide a model-driven testing methodology that supports test automation based on system requirements in NL. Using the methodology, the engineer first specifies system requirements according to Cockburn use case notation [79] and then manually refines them into Use Case Map (UCM) scenario models [80].…”
Section: Related Workmentioning
confidence: 99%
“…Kesserwan et al [78] provide a model-driven testing methodology that supports test automation based on system requirements in NL. Using the methodology, the engineer first specifies system requirements according to Cockburn use case notation [79] and then manually refines them into Use Case Map (UCM) scenario models [80].…”
Section: Related Workmentioning
confidence: 99%
“…To evaluate the extended testing methodology in this work, the experiment method described in [8] is reused to generate the test case. The new obtained result is a trace model (tracemodel.ecore) which relates UCM scenario models to TTCN-3 test cases grouped in test suites.…”
Section: B Traceability Links and Alignment With Test Resultsmentioning
confidence: 99%
“…In this paper, model transformation techniques are used to create traceability links among MBT artifacts during the test generation process. The approach extends previous testing methodology presented in [8] that generates tests based on behavioral models. This paper's contribution is building a traceability model to support the creation and persistence of such relationships among heterogeneous models representing various testing artifacts.…”
Section: Introductionmentioning
confidence: 94%
See 1 more Smart Citation
“…Kesserwan et al [86] provide a model-driven testing methodology that supports test automation based on system requirements in NL. Using the methodology, the engineer first specifies system requirements according to Cockburn use case notation [87] and then manually refines them into Use Case Map (UCM) scenario models [88].…”
Section: Related Workmentioning
confidence: 99%