Testing object‐oriented software: a survey

Binder, Robert V.

doi:10.1002/(sici)1099-1689(199609/12)6:3/4<125::aid-stvr121>3.0.co;2-x

Cited by 99 publications

(41 citation statements)

References 49 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…As more of the specification is acquired, the testing mode moves seamlessly from bounded exhaustive exploration, satisfying the bounded inter-method coverage criterion (Binder, 1996), to bounded exhaustive testing, equivalent to full conformance-testing to an independent finite state specification (Chow, 1978;Holcombe and Ipate, 1998); and the generated test reports become shorter and more focused until full test automation is achieved.…”

Section: Lazy Systematic Unit Testingmentioning

confidence: 99%

“…A complete formal treatment of subtyping and state partitioning, and their relationship to test coverage and process algebra, may be found in (Simons, 2006). Bounded exhaustive unit testing from state-based specifications is tractable (McGregor, 1994), but synthesizing the statespace of entire systems from object state machines produces a state explosion (Binder, 1996) unless a suitable formal strategy is found for partitioning the tests (Holcombe and Ipate, 1998;Ipate and Holcombe, 1997).…”

Section: State-based Testing For Objectsmentioning

confidence: 99%

See 1 more Smart Citation

JWalk: a tool for lazy, systematic testing of java classes by design introspection and user interaction

Simons

2007

Autom Softw Eng

View full text Add to dashboard Cite

Abstract. Popular software testing tools, such as JUnit, allow frequent retesting of modified code; yet the manually created test scripts are often seriously incomplete. A unit-testing tool called JWalk has therefore been developed to address the need for systematic unit testing within the context of agile methods. The tool operates directly on the compiled code for Java classes and uses a new lazy method for inducing the changing design of a class on the fly. This is achieved partly through introspection, using Java's reflection capability, and partly through interaction with the user, constructing and saving test oracles on the fly. Predictive rules reduce the number of oracle values that must be confirmed by the tester. Without human intervention, JWalk performs bounded exhaustive exploration of the class's method protocols and may be directed to explore the space of algebraic constructions, or the intended design state-space of the tested class. With some human interaction, JWalk performs up to the equivalent of fully automated state-based testing, from a specification that was acquired incrementally.

show abstract

Section: Lazy Systematic Unit Testingmentioning

confidence: 99%

Section: State-based Testing For Objectsmentioning

confidence: 99%

JWalk: a tool for lazy, systematic testing of java classes by design introspection and user interaction

Simons

2007

Autom Softw Eng

View full text Add to dashboard Cite

show abstract

“…This has led to comprehensive surveys and taxonomies for very specific types of faults, including program and operating system faults [3], faults in object-oriented software [10], faults in service-based applications [11,14], faults in memory devices [70], or faults in microprocessor design [4]. Event processing, as an emerging research direction, is yet lacking a common model for faults.…”

Section: Introductionmentioning

confidence: 99%

Deriving a unified fault taxonomy for event-based systems

Hummer

Inzinger

Leitner

et al. 2012

Proceedings of the 6th ACM International Conference on Distributed Event-Based Systems

View full text Add to dashboard Cite

Dependability and fault-tolerance, which are key requirements for business-or safety-critical applications, require explicit knowledge of potential faults that may occur within a system. In contrast to other major research directions, the emerging field of distributed event-based systems is yet lacking a common understanding of faults. In this paper we take a step forward and study potential origins and effects of faults in such systems. Our work on a unified fault taxonomy follows a rigorous methodology. We first identify five core sub-areas in the broader field of event-based systems, and discuss commonalities and differences among them. Then we derive from the existing literature a coherent domain model, which accurately captures the specifics of the different areas. The domain model provides a holistic view and covers both structural and procedural aspects of event-based systems. Based on this model, we elaborate a detailed taxonomy of faults, in line with well-established fault dimensions from dependable and secure computing. The fault taxonomy forms the basis for a comprehensive discussion of fault instances across the five sub-areas of event processing.

show abstract

“…Object-oriented software presents a variety of new challenges for testing, compared to testing for procedural software [1]. For example, programs contain complex interactions among sets of collaborating objects from different classes.…”

Section: Introductionmentioning

confidence: 99%

“…For example, programs contain complex interactions among sets of collaborating objects from different classes. It is not sufficient to test a class in isolation-testing the interactions between instances of different classes is of critical importance [2,1,3]. A variety of techniques can be employed to test different aspects of object interactions.…”

Section: Introductionmentioning

confidence: 99%

Coverage Criteria for Testing of Object Interactions in Sequence Diagrams

Rountev

Kagan

Sawin

2005

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. This work defines several control-flow coverage criteria for testing the interactions among a set of collaborating objects. The criteria are based on UML sequence diagrams that are reverse-engineered from the code under test. The sequences of messages in the diagrams are used to define the coverage goals for the family of criteria, in a manner that generalizes traditional testing techniques such as branch coverage and path coverage. We also describe a run-time analysis that gathers coverage measurements for each criterion. To compare the criteria, we propose an approach that estimates the testing effort required to satisfy each criterion, using analysis of the complexity of the underlying sequence diagrams. The criteria were investigated experimentally on a set of realistic Java components. The results of this study compare different approaches for testing of object interactions and provide insights for testers and for builders of test coverage tools.

show abstract

Testing object‐oriented software: a survey

Cited by 99 publications

References 49 publications

JWalk: a tool for lazy, systematic testing of java classes by design introspection and user interaction

JWalk: a tool for lazy, systematic testing of java classes by design introspection and user interaction

Deriving a unified fault taxonomy for event-based systems

Coverage Criteria for Testing of Object Interactions in Sequence Diagrams

Contact Info

Product

Resources

About