Untitled

White, Lee; Offutt, Jeff; Yates, Derek; Hierons, Robert M.; Hennell, Michael; Mitchell, Peter

doi:10.1002/stvr.v16:4

Cited by 8 publications

(1 citation statement)

References 0 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: 99%

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: 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

Automatically testing interacting software components

Gallagher

Offutt

2006

Proceedings of the 2006 International Workshop on Automation of Software Test

View full text Add to dashboard Cite

One goal of integration testing for object-oriented software is to ensure high object interoperability. Sent messages should have the intended effects on the states and subsequent actions of the receiving objects. This is especially difficult when software is comprised of components developed by different vendors, with different languages, and the implementation sources are not all available. A previous paper presented a model of inter-operating OO classes based on finite state machines. It addresses methods for identifying the relevant actions of a test component to be integrated into the system, transforms the finite state specification into a control and data flow graph, labels the graph with all def s and uses of class variables, and presents an algorithm to generate test specifications as specific paths through the directed graph. It also presents empirical results from an automatic tool that was built to support this test method. This paper presents additional details about the tool itself, including how several difficult problems were solved, and adds new capabilities to help automate the transformation of test specifications into executable test cases. The result is a fresh approach to automated testing. It follows accepted theoretical procedures while operating directly on an objectoriented software specification. This yields a data flow graph and executable test cases that adequately cover the graph according to classical graph coverage criteria. The tool supports specification-based testing and helps to bridge the gap between theory and practice.

show abstract