Pairwise structural testing of object and aspect-oriented Java programs

Abstract

Most structural testing approaches are targeted at units of implementation (i.e., unit testing). A problem that is not addressed by unit testing is the interaction among units, with respect to the correctness of their interfaces. We present a structural integration testing approach for object-oriented (OO) and aspect-oriented (AO) Java programs as an extension of a unit testing approach we have developed before. To make the activity feasible, instead of considering arbitrary call depths, we address the testing of pairs of units. We propose a model called PWDU (PairWise Def-Use) graph to represent the control and data-flow of pairs of units. Based on the PWDU , three testing criteria are defined: all-pairwise-integrated-nodes, all-pairwise-integrated-edges (controlflow based criteria), and all-pairwise-integrated-uses (a data-flow based criterion). We also present the implementation of our approach as an extension to the Java Bytecode Understanding and Testing (JaBUTi) family of testing tools along with an example of usage.

Integration Testing of Aspect-Oriented Programs: a Structural Pointcut-Based Approach

“…The example shows evidence that the pointcut-based approach is effective in finding AO specific faults, when compared with unit testing criteria. A preliminary cost evaluation of a previous work on which the approach presented in this paper is related [Franchin et al 2007], shows that the cost of application of the criteria is relatively low [Lemos et al 2008]. These two sets of results summed with the extension of the JaBUTi tool, which shows evidence of the feasibility of the approach, represent a preliminary evaluation that motivates the application of our model and criteria.…”

“…(2) the generation of the PCCFG graph; (3) the implementation of the criteria; and (4) the implementation of the pointcut-based testing environment. The extension is being made on top of the pairwise integration testing version of JaBUTi -the PW-AJ version [Franchin et al 2007]. In fact, the extension is already functional, missing only the displaying of the PCCFG graphs.…”

“…Franchin et al [Franchin et al 2007] presented a pairwise integration testing approach for Object-Oriented (OO) and AO Java programs that builds on top of the unit testing approach referred to in the last section. A model to represent pairs of interacting units (called Pair-Wise Def-Use Graph -PWDU) was proposed, and a family of structural testing criteria was defined based on such model.…”

“…For instance, to have more confidence that an access control concern has been thoroughly tested in a program P , it is important to know the coverage of the structure of the corresponding advice at each join point. Based on the pairwise approach discussed before [Franchin et al 2007], we propose the representation of all pairs of interacting units related to each advice in a single model. The idea is to help understanding and testing the pieces of advice at each join point of the program.…”

“…Thus, the natural testing strategy to be followed in this context would be: (1) focus on each unit by testing each method and advice in isolation (by using, for instance, the criteria proposed before [Lemos et al 2007, Vincenzi et al 2005, Vincenzi et al 2006); (2) focus on the crosscutting concerns by testing each advice at each selected join point. Afterwards, to have more confidence in the program and to consider the integration of methods, the pairwise testing criteria proposed by Franchin et al [Franchin et al 2007] could also be used. Note that, to have a more efficient testing activity, the test set used in the precedent level can be used as a starting point for the next level.…”