2015 IEEE/ACM 37th IEEE International Conference on Software Engineering 2015
DOI: 10.1109/icse.2015.28
|View full text |Cite
|
Sign up to set email alerts
|

Making System User Interactive Tests Repeatable: When and What Should We Control?

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
12
0

Year Published

2016
2016
2022
2022

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 30 publications
(12 citation statements)
references
References 29 publications
0
12
0
Order By: Relevance
“…Several authors have commented on the reasons for this flakiness [28,37,46,56,62], finding that one of the most common causes lies in the prevalent use of asynchronous waits; functions make asynchronous calls to services, but may not wait sufficient time for those services to respond, producing a different result to that had they waited slightly longer.…”
Section: Crash Reproduction Workflowmentioning
confidence: 99%
“…Several authors have commented on the reasons for this flakiness [28,37,46,56,62], finding that one of the most common causes lies in the prevalent use of asynchronous waits; functions make asynchronous calls to services, but may not wait sufficient time for those services to respond, producing a different result to that had they waited slightly longer.…”
Section: Crash Reproduction Workflowmentioning
confidence: 99%
“…An important difference between verification and testing derives from the way in which execution has increasingly become nondeterministic. Whereas programming languages have included new semantic features that have posed novel challenges for verification research and practice, the dramatic increase in the stochastic behaviour of most deployed systems, over a similar period, has posed challenges for software testing; tests are 'flaky' [50], [87], [100]. In this section we explore this test-specific challenge, which can be summarised with the aphorism: Assume all Tests Are Flaky (ATAF).…”
Section: Survive and Thrive Even When We Assume Tests Are Flaky mentioning
confidence: 99%
“…Gao et al [50] consider the related problem of understanding the impact of flakiness at different layers (user interaction layer, behavioural layer, and code layer), concluding that testers should do their best to control flakiness at each level.…”
Section: A Prior Work On the Flakiness Problemmentioning
confidence: 99%
“…In other words, for an identical system-call with the same input parameters, several possible execution paths may exist. Conse-quently, it is no longer feasible to assess the correctness of this type of systems with a unique iteration of a testcase for each combination of input parameters [30]. Besides, it is challenging (if feasible) to force the execution of a specific path.…”
Section: Problem Statementmentioning
confidence: 99%