Lecture Notes in Computer Science
DOI: 10.1007/978-3-540-70889-6_17
|View full text |Cite
|
Sign up to set email alerts
|

Making Model-Based Testing More Agile: A Use Case Driven Approach

Abstract: Abstract. We address the problem of misalignment of artifacts developed in agile software development projects and those required by model-based test generation tools. Our solution is domain specific and relies on the existence of domain experts to design the test models. The testers interface the test generation systems with use cases that are converted into sequences of so called action words corresponding to user events at a high level of abstraction. To support this scheme, we introduce a coverage language… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
17
0
4

Publication Types

Select...
3
2
1

Relationship

2
4

Authors

Journals

citations
Cited by 16 publications
(21 citation statements)
references
References 9 publications
0
17
0
4
Order By: Relevance
“…On the other hand, it seems especially important to provide easy-to-use tools and services that do not place an additional burden, such as that of test modeling, on the project personnel. We have identified a minimum of three modes [11] to be supported in agile processes: smoke testing should be performed in each continuous integration cycle; user stories can be tested in a usecase testing mode; and there should be a bug hunting mode, whose only purpose is to support finding defects efficiently in long test runs.…”
Section: Domain-specific Mbtmentioning
confidence: 99%
See 3 more Smart Citations
“…On the other hand, it seems especially important to provide easy-to-use tools and services that do not place an additional burden, such as that of test modeling, on the project personnel. We have identified a minimum of three modes [11] to be supported in agile processes: smoke testing should be performed in each continuous integration cycle; user stories can be tested in a usecase testing mode; and there should be a bug hunting mode, whose only purpose is to support finding defects efficiently in long test runs.…”
Section: Domain-specific Mbtmentioning
confidence: 99%
“…Currently, we have implemented three heuristics which allow us to experiment with the tools: a purely random heuristics that can be used in bug hunting mode, and two heuristics based on game-theory [11] to be used in the use case testing mode: a single thread and a two thread version. The difference between the two is that the latter continues to search an optimal path to a state fulfilling the coverage requirement, while the other thread waits for a return value from the client executing a keyword.…”
Section: Overview Of the Toolsmentioning
confidence: 99%
See 2 more Smart Citations
“…The background of our approach has been introduced previously in [6,7,8,9]. In this paper, based on [5], we concentrate on the test model library.…”
Section: Introductionmentioning
confidence: 99%