If A Fails, Can B Still Succeed? Inferring Dependencies between Test Results in Automotive System Testing

Arlt, Stephan; Morciniec, Tobias; Podelski, Andreas; Wagner, Silke

doi:10.1109/icst.2015.7102593

Cited by 14 publications

(13 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The result of each test case during execution, when combined with the dependency information, enables us to dynamically identify which test case to execute next. The idea of using dependency information in identifying redundant test cases is also evaluated and confirmed by Arlt et al [8] where dependency relationships are derived and inferred from a structured requirements specification.…”

Section: Background and Preliminariesmentioning

confidence: 98%

“…Moreover, our approach assumes that test case dependencies are identified, either manually or otherwise. We did not assess the cost of identifying these dependencies but in cases where more complex dependencies exist, an automatic inference and extraction of dependencies is more feasible, see e.g., Arlt and Morciniec [8].…”

Section: A Delimitationsmentioning

confidence: 99%

“…Two applications of their proposed approach are possible: general test case selection and test case prioritization for regression testing. Arlt et al [8] use logical dependencies between requirements written in a structured format to automatically detect a redundant test case. Their approach is essentially a test suite reduction technique based on the current status of successful tests and failed tests.…”

Section: Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Dynamic Integration Test Selection Based on Test Case Dependencies

Tahvili

Saadatmand²,

Larsson³

et al. 2016

2016 IEEE Ninth International Conference on Software Testing, Verification and Validation Workshops (ICSTW)

View full text Add to dashboard Cite

Prioritization, selection and minimization of test cases are well-known problems in software testing. Test case prioritization deals with the problem of ordering an existing set of test cases, typically with respect to the estimated likelihood of detecting faults. Test case selection addresses the problem of selecting a subset of an existing set of test cases, typically by discarding test cases that do not add any value in improving the quality of the software under test. Most existing approaches for test case prioritization and selection suffer from one or several drawbacks. For example, they to a large extent utilize static analysis of code for that purpose, making them unfit for higher levels of testing such as integration testing. Moreover, they do not exploit the possibility of dynamically changing the prioritization or selection of test cases based on the execution results of prior test cases. Such dynamic analysis allows for discarding test cases that do not need to be executed and are thus redundant. This paper proposes a generic method for prioritization and selection of test cases in integration testing that addresses the above issues. We also present the results of an industrial case study where initial evidence suggests the potential usefulness of our approach in testing a safety-critical train control management subsystem.

show abstract

Section: Background and Preliminariesmentioning

confidence: 98%

Section: A Delimitationsmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Dynamic Integration Test Selection Based on Test Case Dependencies

Tahvili

Saadatmand²,

Larsson³

et al. 2016

2016 IEEE Ninth International Conference on Software Testing, Verification and Validation Workshops (ICSTW)

View full text Add to dashboard Cite

show abstract

“…Figure 1: The steps of the proposed approach cases give partial information on the verdict of a test case from the verdict of another one. Arlt et al in [2] showed that test cases will be failed after each other if the testers do not care about the dependency between test cases. In integration testing, the software modules are combined and tested as a group, therefore, the problem of detecting the dependency between test cases will be more highlighted for the testers.…”

Section: Inputmentioning

confidence: 99%

“…By having an overview of dependent test cases, we can prioritize, select, and schedule test cases for execution. Some previous studies show that, there are different types of dependency between test cases, which will impact the result of a test execution [2]. In our previous work [15] we proposed a manual method for measuring the degree of dependency between test cases.…”

Section: Introductionmentioning

confidence: 99%

Cluster-based test scheduling strategies using semantic relationships between test specifications

Tahvili

Hatvani

Felderer

et al. 2018

Proceedings of the 5th International Workshop on Requirements Engineering and Testing

View full text Add to dashboard Cite

One of the challenging issues in improving the test efficiency is that of achieving a balance between testing goals and testing resources. Test execution scheduling is one way of saving time and budget, where a set of test cases are grouped and tested at the same time. To have an optimal test execution schedule, all related information of a test case (e.g. execution time, functionality to be tested, dependency and similarity with other test cases) need to be analyzed. Test scheduling problem becomes more complicated at high-level testing, such as integration testing and especially in manual testing procedure. Test specifications are generally written in natural text by humans and usually contain ambiguity and uncertainty. Therefore, analyzing a test specification demands a strong learning algorithm. In this position paper, we propose a natural language processing-based approach that, given test specifications at the integration level, allows automatic detection of test cases semantic dependencies. The proposed approach utilizes the Doc2Vec algorithm and converts each test case into a vector in n-dimensional space. These vectors are then grouped using the HDBSCAN clustering algorithm into semantic clusters. Finally, a set of cluster-based test scheduling strategies are proposed for execution. The proposed approach has been applied in a subsystem from the railway domain by analyzing an ongoing testing project at Bombardier Transportation AB, Sweden.

show abstract