Test Suite Prioritization for Efficient Regression Testing of Model-Based Automotive Software

Objective: From the literature review, it is evident that the concept of “regression testing” inherited in agile software testing originates from software maintenance practices. Therefore, the existing algorithms for regression testing revolve around the software maintenance principles rather than agile methodology. The objective of this paper is to evaluate the degree of fitness of the existing regression test-suite development algorithms for performing the regression testing in agile. Methods: This paper performs a systematic literature review for research work published from 2006 to 2018, which includes survey of the existing regression testing algorithms to identify and overcome the challenges associated with them while performing regression testing in agile. This research paper considers the four research questions into scope for analyzing the fitness of existing regression test-suite development algorithm for performing regression testing under agile methodology. Further, this paper attempts to propose approach for the development of the regression test-suite suitable for regression testing under agile methodology. Results: The current regression test-suite development algorithm were found unsuitable for performing the regression testing under agile methodology due to the newly identified four key challenges associated with them. Conclusion: The current regression test-suite development algorithms aligned with software maintenance principles rather than agile methodology. In addition, the newly proposed approach for regression test-suite development found to be easily adaptable by agile teams as it aligns with agile methodology principles. Finally, this paper recommends the adoption of agile principle through the newly proposed approach for developing regression test-suite for performing regression testing under agile methodology.

Download Full-text

Quality Improvement in Automotive Software Engineering Using a Model-Based Approach

Model-Driven Software Development ◽

10.4018/978-1-60566-006-6.ch015 ◽

2009 ◽

pp. 374-399 ◽

Cited By ~ 1

Author(s):

Tibor Farkas

Keyword(s):

Quality Assurance ◽

Software Engineering ◽

Object Constraint Language ◽

Automotive Software ◽

Model Based ◽

Control Units ◽

Preventive Actions ◽

Automotive Software Engineering ◽

Automotive Control Software ◽

Assurance Process

Premium quality and innovation are the cornerstones of the leading positions of car manufacturers and suppliers in the world market. The permanently increasing complexity of in-car electronics and the rapidly growing amount of automotive software running on embedded electronic control units, places higher demands on quality assurance for the future. Quality cannot be implemented into software on embedded control units after their development. Methods for defects detection have to be constituted to automatically stop development to fix a problem before the defect continues downstream. In addition preventive actions have to be taken in respect of front-loading quality and reliability. An automatic and tool independent check of custom development rules, quality standards and enterprise wide guidelines can support the quality assurance process in the development of automotive control software. In the domain of automotive software engineering there is a lack of automated checking for standard conformance. Especially, a formal and tool independent notation of rules to follow is missing. In this chapter, the model-based design of automotive vehicle functions is taken as an example to show how textual rules describing development standards to be met can be transformed into a formal notation using the open standards Meta Object Facility and Object Constraint Language. Thereafter these rules can be checked automatically. The feasibility of this approach is shown by a software demonstrator.

Download Full-text

Test Pair Selection for Test Case Prioritization in Regression Testing for WS-BPEL Programs

International Journal of Web Services Research ◽

10.4018/jwsr.2013010104 ◽

2013 ◽

Vol 10 (1) ◽

pp. 73-102 ◽

Cited By ~ 8

Author(s):

Lijun Mei ◽

Yan Cai ◽

Changjiang Jia ◽

Bo Jiang ◽

W.K. Chan

Keyword(s):

Web Services ◽

Structural Similarity ◽

Regression Testing ◽

Test Pair ◽

Test Suite ◽

Test Case ◽

Test Cases ◽

Test Case Prioritization ◽

Empirical Results ◽

Selection For

Many web services not only communicate through XML-based messages, but also may dynamically modify their behaviors by applying different interpretations on XML messages through updating the associated XML Schemas or XML-based interface specifications. Such artifacts are usually complex, allowing XML-based messages conforming to these specifications structurally complex. Testing should cost-effectively cover all scenarios. Test case prioritization is a dimension of regression testing that assures a program from unintended modifications by reordering the test cases within a test suite. However, many existing test case prioritization techniques for regression testing treat test cases of different complexity generically. In this paper, the authors exploit the insights on the structural similarity of XML-based artifacts between test cases in both static and dynamic dimensions, and propose a family of test case prioritization techniques that selects pairs of test case without replacement in turn. To the best of their knowledge, it is the first test case prioritization proposal that selects test case pairs for prioritization. The authors validate their techniques by a suite of benchmarks. The empirical results show that when incorporating all dimensions, some members of our technique family can be more effective than conventional coverage-based techniques.

Download Full-text