Profiting from Unit Tests for Integration Testing

Holling, Dominik; Hofbauer, Andreas; Pretschner, Alexander; Gemmar, Matthias

doi:10.1109/icst.2016.28

Cited by 6 publications

(2 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Holling et al [125] address the integration test stage by introducing the OUTFIT tool. The aim of this approach is to achieve higher coverage in integration testing and early detection of errors.…”

Section: B Fault-based Approachesmentioning

confidence: 99%

Survey of Model-Based Security Testing Approaches in the Automotive Domain

2023

View full text Add to dashboard Cite

Modern connected or autonomous vehicles (AVs) are highly complex cyber-physical systems. As a result of the high number of different technologies and connectivity features involved, testing these systems to identify security vulnerabilities is a big challenge. Security testing techniques, such as penetration testing, are often manual methods that are applied comparatively late in the vehicle development process. Thus, vulnerabilities are only detected late or after development, leading to higher costs and more patching effort. To reduce the amount of testing resources in general and enable early and automated testing, modelbased testing methods have been established in several domains, such as information technology and the automotive domain. The transfer of model-based testing approaches to automotive security testing could help to detect vulnerabilities earlier than other, manual methods by automatically generating, executing, or simulating security tests. In this study, we review the literature on model-based test approaches in the automotive domain. First, we consider security-independent approaches to obtain an overview of applied models, formalisms, test selection criteria, and test generation techniques. In addition, we investigate, whether and how model-based approaches are applied for automotive security testing. Overall, we identified 63 publications related to model-based testing and 29 publications with regard to model-based security testing. The aim of this study is to provide an overview and direct comparison between these approaches. In this manner, the state of model-based security testing in the automotive domain, current challenges, and potential research areas are determined. INDEX TERMSAutomotive security, model-based testing, model-based security testing.

show abstract

Section: B Fault-based Approachesmentioning

confidence: 99%

Survey of Model-Based Security Testing Approaches in the Automotive Domain

2023

View full text Add to dashboard Cite

show abstract

“…This may help to concentrate on the logic of the test rather than the structure of it, similar to static code analysing tools that can highlight potential problems with the syntax of the code. Another automated tool, called OUTFIT, was created by Holling et al [11] which creates integration tests automatically, based on unit tests with a high coverage metric. They applied their approach to an engine control system and they showed that this automated procedure has the potential to flag unused and superfluous code fragments.…”

mentioning

confidence: 99%

A practical guide towards agile test-driven development for scientific software projects

Teschner

2020

Preprint

View full text Add to dashboard Cite

Software testing has received much attention over the last years and has reached such critical importance that agile software development practices put software testing at its core. Agile software development is successfully applied in large-scale industrial software developments but due to its granular responsibilities with roles assigned to various members of the development team, these practices may not be applicable to scientific code development, especially in an academic environment, where it is not uncommon that the codebase is developed, maintained and used by a single person. Even for collaborative scientific software development, financed through external grants, the end-users are typically still part of the development team. This is in contrast to how software is developed in many industries, where the development team and end-users are two separate entities. There are, however, many good code development practices that can be adopted for scientific software projects. Specifically, the intention of this article is to take the centrepiece of agile software development -the test-driven development -and tailor it to scientific and academic, single-user code development. In this study, a c++ starter project is developed and made available, based on the meson build system, which provides native support for software testing. It is used to show how a simple linear algebra application, found in many scientific and academic applications, can be developed and how simple unit, integration and system tests can be created that are managed through the meson build system. In this way, we are able to minimise software defects and reduce the risk to interpret incorrect data generated by erroneous software that may result, in the worst case, in the wrong conclusions to be drawn. Each layer of testing presents one additional layer of protection against such software defects and we will explore how these may be incorporated with minimum overhead to produce bug-free software.

show abstract

On the Replicability of Experimental Tool Evaluations in Model-Based Development

Boll

Kehrer

2020

Communications in Computer and Information Science

View full text Add to dashboard Cite

Profiting from Unit Tests for Integration Testing

Cited by 6 publications

References 22 publications

Survey of Model-Based Security Testing Approaches in the Automotive Domain

Survey of Model-Based Security Testing Approaches in the Automotive Domain

A practical guide towards agile test-driven development for scientific software projects

On the Replicability of Experimental Tool Evaluations in Model-Based Development

Contact Info

Product

Resources

About