A Test Strategy for Object-Oriented Programs

Authors:
Affiliations:
Venue:
COMPSAC '95 Proceedings of the 19th International Computer Software and Applications Conference
Year:
1995

Citing 0
Cited 8

In black and white: an integrated approach to class-level testing of object-oriented programs

ACM Transactions on Software Engineering and Methodology (TOSEM)
TACCLE: a methodology for object-oriented software testing at the class and cluster levels

ACM Transactions on Software Engineering and Methodology (TOSEM)
Object-oriented integration testing

Annals of Software Engineering
Coupling-based class integration and test order

Proceedings of the 2006 international workshop on Automation of software test
The implementation of an extensible system for comparison and visualization of class ordering methodologies

Journal of Systems and Software
A Pareto ant colony algorithm applied to the class integration and test order problem

ICTSS'10 Proceedings of the 22nd IFIP WG 6.1 international conference on Testing software and systems
Establishing integration test orders of classes with several coupling measures

Proceedings of the 13th annual conference on Genetic and evolutionary computation
A layer-based method for rapid software development

Computers & Mathematics with Applications

Quantified Score

Hi-index	0.00

Visualization

Abstract

The complexity and interdependencies of an object-oriented program makes testing of such programs difficult. In this paper, we present a reverse engineering based model called Object Relation Diagram (ORD), which is generated from analyzing the C++ source code of an object-oriented program. An ORD is a directed graph in which the vertices represent the object classes and the edges represent the relationships among the object classes. Based on the ORD, a test strategy, called test order, for unit testing and integration testing of object-oriented programs is described. The test order algorithm uses topological sorting and clusters of strongly connected subgraphs of the ORD. It computes the optimal test order in the sense that the effort required to construct the test stubs to simulate the untested classes/member functions is minimum. We show the savings of the test strategy through statistics of the InterViews library.