Integrating Component Tests to System Tests

Schätz, Bernhard; Pfaller, Christian

doi:10.1016/j.entcs.2009.12.040

Cited by 13 publications

(9 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…There is a lot of research on integration testing, from a MBT perspective [1,23,5,3,13,15] or not [12,2,6,21,18,17,20], but we could not find articles analyzing in detail how Parnas's uses relation and the Z notation can be used for integration testing. Clements and others [7, pages 68-71] pay attention to the uses relation and remark its importance in integration testing.…”

Section: Related Workmentioning

confidence: 91%

See 1 more Smart Citation

Integration Testing in the Test Template Framework

Cristiá

Mesuro

Frydman³

2014

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. The Test Template Framework (TTF) is a model-based testing method for the Z notation, originally proposed for unit testing. In this paper we analyze how the TTF can be extended to integration testing. Since integration testing is related to software design, we decided to investigate the relation between the TTF and the uses relation, a key element in David Parnas' design theory. We propose how a Z specification should be structured for the TTF to be able to generate integration tests by following the uses relation. The problem of stub generation and the kinds of errors that these integration tests can discover are also discussed.

show abstract

Section: Related Workmentioning

confidence: 91%

“…Testing components that can only be accessed through a system interface is the goal of the work by Schätz and Pfaller [23]. They use transition systems to model the behavior of components and hierarchical transition systems to model component interactions.…”

Section: Related Workmentioning

confidence: 99%

Integration Testing in the Test Template Framework

Cristiá

Mesuro

Frydman³

2014

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

show abstract

“…However, before integrating third party components into a system there may be a need for internal testing on the component level [15]. Since this sometimes requires new, potentially tailor-made testing environments for the third party components, the cost for creating these new environments on the component level cannot be justified.…”

Section: A Published Work On Vertical Test Reuse For Embedded Systemsmentioning

confidence: 99%

“…Since this sometimes requires new, potentially tailor-made testing environments for the third party components, the cost for creating these new environments on the component level cannot be justified. In Section III-C we describe an approach found in [15] that addresses this problem.…”

Section: A Published Work On Vertical Test Reuse For Embedded Systemsmentioning

confidence: 99%

Vertical Test Reuse for Embedded Systems: A Systematic Mapping Study

Flemström

Sundmark

Afzal

2015

2015 41st Euromicro Conference on Software Engineering and Advanced Applications

View full text Add to dashboard Cite

Abstract-Vertical test reuse refers to the the reuse of test cases or other test artifacts over different integration levels in the software or system engineering process. Vertical test reuse has previously been proposed for reducing test effort and improving test effectiveness, particularly for embedded system development. The goal of this study is to provide an overview of the state of the art in the field of vertical test reuse for embedded system development. For this purpose, a systematic mapping study has been performed, identifying 11 papers on vertical test reuse for embedded systems. The primary result from the mapping is a classification of published work on vertical test reuse in the embedded system domain, covering motivations for reuse, reuse techniques, test levels and reusable test artifacts considered, and to what extent the effects of reuse have been evaluated.

show abstract

“…The component architecture (SCA) approaches (Ding et al, 2008) emphasize the service concept, like Kmelia does; but unfortunately contract features are not introduced yet in SCA. Testing LTS behaviours is performed in (Schätz and Pfaller, 2010). The authors customize component testing at the level of component in a system use.…”

Section: Related Workmentioning

confidence: 99%

Combining Techniques to Verify Service-based Components

André

Attiogbé

Mottu

2017

Proceedings of the 5th International Conference on Model-Driven Engineering and Software Development

View full text Add to dashboard Cite

Abstract:Early verification is essential in model-driven development because late error detection involves a costly correction and approval process. Modelling real life systems covers three aspects of a system (structure, dynamics and functions) and one verification technique is not sufficient to check the properties related to these aspects. Considering Service-based Component Models, we propose a unifying schema called multi-level contracts that enables a combination of verification techniques (model checking, theorem proving and model testing) to cover the V&V requirements. This proposal is illustrated using the Kmelia language and its COSTO tool.

show abstract

Integrating Component Tests to System Tests

Cited by 13 publications

References 8 publications

Integration Testing in the Test Template Framework

Integration Testing in the Test Template Framework

Vertical Test Reuse for Embedded Systems: A Systematic Mapping Study

Combining Techniques to Verify Service-based Components

Contact Info

Product

Resources

About