Testing Of Object-oriented Programs Research Articles

An integration test coverage metric for Java programs

A large number of test coverage metrics have been proposed in the context of unit and system testing of object-oriented programs. However, structural coverage metrics for integration testing have scarcely been reported. On the other hand, interface bugs are known to be one of the most insidious. In this context, we propose a suite of integration test coverage metrics based on the coverage of data and control dependency edges of the JSysDG (Java System Dependency Graph). We also define a metric that additionally uses the state machine models of the given classes to be integrated. We present our experimental results and a comparison of our metrics with related metrics.

TECHNOLOGY FOR DESIGN OF THE EMULATOR FOR DEBUGGING OF MICROCONTROLLERS

The technique for development of emulators for debug boards intended for microcontrollers investigations to obtain optimal characteristics and parameters of the developed product is reviewed. The core approaches to testing of object-oriented programs are analyzed, a method for testing a software application for debugging microcontrollers is described. The results of the tests and their quantitative characteristics are given. A hands-on example of the proposed technology for developing software emulators is described.

A Novel Approach of Mutation Testing of Object-Oriented Programs

Mutation testing is a powerful but complicated and computationally expensive testing method. Testing of object-oriented software has a number of features that make it different from conventional software testing. The factors like inheritance, encapsulation, polymorphism, which are the specialized phenomena of object- oriented software bring in the point of different. Mutation testing is a fault-based testing technique that has the advantage of easy automation, and can check the thoroughness of testing performed using other testing approaches. Mutation operators are an important consideration while designing the mutation testing methodologies. This paper presents mutation operators, testing techniques, available tools and the current research directions.

Equality to Equals and Unequals: A Revisit of the Equivalence and Nonequivalence Criteria in Class-Level Testing of Object-Oriented Software

Algebraic specifications have been used in the testing of object-oriented programs and received much attention since the 1990s. It is generally believed that class-level testing based on algebraic specifications involves two independent aspects: the testing of equivalent and nonequivalent ground terms. Researchers have cited intuitive examples to illustrate the philosophy that even if an implementation satisfies all the requirements specified by the equivalence of ground terms, it may still fail to satisfy some of the requirements specified by the nonequivalence of ground terms. Thus, both the testing of equivalent ground terms and the testing of nonequivalent ground terms have been considered as significant and cannot replace each other. In this paper, we present an innovative finding that, given any canonical specification of a class with proper imports, a complete implementation satisfies all the observationally equivalent ground terms if and only if it satisfies all the observationally nonequivalent ground terms. As a result, these two aspects of software testing cover each other and can therefore replace each other. These findings provide a deeper understanding of software testing based on algebraic specifications, rendering the theory more elegant and complete. We also highlight a couple of important practical implications of our theoretical results.

Testing object-oriented programs: from formal specification to test scenario generation

New problems associated with the testing and maintenance of object-oriented programs (OOPs) have been introduced with the dramatically increasing use of OOPs over the past decade. Testing OOPs beyond the class level has been rarely discussed. This paper presents an approach performing high level testing for OOPs based on formal specifications and usage profiles. The behavior of a software system is specified in an object-oriented formal specification. A state model provides a complementary representation of the dynamic behavior. In the model, a state represents the cumulative results of the system behavior. Probability distributions are used to derive the anticipated operation sequences of a program from the state model. An enhanced state transition diagram (ESTD) is used to describe the state model, which incorporates hierarchy, usage and parameter information. This paper describes the construction of state transition diagrams (STDs) based on the formal specification, and the derivation of test scenarios from the ESTD.

Issues in porting software from c to c++

SUMMARY This paper describes an experiment in the development of a small piece of software in both the languages C and C + + in a university setting. The C+ + codes were found to he more modular than the corresponding C codes. Some of the other effects of C++ on program quality are very briefly discussed. The paper also discusses some of the errors that C programmers may make as novice C++ programmers, and the testing of object-oriented programs. Some of the error types possible in C++, but not in C, include delays in the flushing of output buffers and polymorphism.