2009
DOI: 10.1007/978-3-642-01702-5_18
|View full text |Cite
|
Sign up to set email alerts
|

Synthesizing Test Models from Test Cases

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2011
2011
2018
2018

Publication Types

Select...
4
1
1

Relationship

2
4

Authors

Journals

citations
Cited by 10 publications
(6 citation statements)
references
References 8 publications
0
6
0
Order By: Relevance
“…Moreover, semi‐automatic generation of test models from existing test assets, such as conventional test cases, needs further elaboration (see, e.g. an approach by Jääskeläinen et al 37). Another issue is incremental testing, i.e.…”
Section: Discussionmentioning
confidence: 99%
“…Moreover, semi‐automatic generation of test models from existing test assets, such as conventional test cases, needs further elaboration (see, e.g. an approach by Jääskeläinen et al 37). Another issue is incremental testing, i.e.…”
Section: Discussionmentioning
confidence: 99%
“…The model synthesis process proposed in [9] is based on pre-existing test cases that are linear sequences of automatically executable steps (keywords), and consists of five phases: First, keywords used in test cases are identified and classified. Second, part of the information in the test cases (such as input data) is separated into variables.…”
Section: Synthesis From Test Casesmentioning
confidence: 99%
“…Although this method works, it relies on a significant amount of manual effort. In particular, the separation of variables requires significant work and skill [9]. Also, the tester has to confirm the merges between the test cases manually, as the state sequence method may generate false positives [9].…”
Section: Synthesis From Test Casesmentioning
confidence: 99%
See 1 more Smart Citation
“…From these test cases the set of paths has been derived. This approach, much like [11], might lead to the requirements loss since test cases are usually written by SWQA which might misinterpret or omit important information. Such an application also requires a lot of refactoring of already existing automation code.…”
Section: A Selection Of the Formal Notationmentioning
confidence: 99%