2011 Fourth IEEE International Conference on Software Testing, Verification and Validation 2011
DOI: 10.1109/icst.2011.27
|View full text |Cite
|
Sign up to set email alerts
|

Improving Regression Testing Transparency and Efficiency with History-Based Prioritization -- An Industrial Case Study

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

2
49
0

Year Published

2015
2015
2022
2022

Publication Types

Select...
3
3
1

Relationship

0
7

Authors

Journals

citations
Cited by 44 publications
(51 citation statements)
references
References 23 publications
2
49
0
Order By: Relevance
“…Selection can be based on properties such as code coverage [14], most likely or expected locations of faults [16], topic coverage [8] or historic test execution data [3]. Prioritization can be viewed as a type of selection, as the first tests in an ordered suite may be the only ones run.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Selection can be based on properties such as code coverage [14], most likely or expected locations of faults [16], topic coverage [8] or historic test execution data [3]. Prioritization can be viewed as a type of selection, as the first tests in an ordered suite may be the only ones run.…”
Section: Related Workmentioning
confidence: 99%
“…Prioritization can be viewed as a type of selection, as the first tests in an ordered suite may be the only ones run. Overviews of selection and prioritization techniques appear in [21], [3], and [4].…”
Section: Related Workmentioning
confidence: 99%
“…In order to analyze the economic feasibility of our approach, we carried out a case study at Bombardier Transportation (BT) in Sweden, inspired by the guidelines of Runeson and Höst [28] and specifically the way guidelines are followed in the paper by Engström et al [4]. We investigated the software/hardware integration testing process for the train control management subsystem (TCMS) in the Trenitalia Frecciarossa 1000, a non-articulated high-speed trainset.…”
Section: Case Studymentioning
confidence: 99%
“…Numerous techniques for test case selection and prioritization have been proposed in the last decade [2], [3], [4]. Most of the proposed techniques for ordering test cases are offline, meaning that the order is decided before execution while the current execution results do not play a part in prioritizing or selecting test cases to execute.…”
Section: Introductionmentioning
confidence: 99%
“…[8]. Prioritization criteria may be based on test case history [9], coverage [10], fault severity [11], customer requirements [12] or costs [13].…”
mentioning
confidence: 99%