Using aspects for testing nonfunctional requirements in object-oriented systems

Software testing is one of the most time consuming activities in the software development cycle. Current research suggests that aspect-oriented programming (AOP) can enhance testing and has the potential to be more effective than macros or test interfaces. There are two major weaknesses when using aspects which are the inability of aspect code to be woven at all execution points and the lack of direct support for interweaving aspects with other aspects. In this paper we address the two major weaknesses and provide a means to overcome them. In addition, current research has focused only on using aspects to test functional requirements (FRs) and paid little attention to nonfunctional requirements (NFRs). In this paper we perform a feasibility study of using aspects to test NFRs which is based on two categorizations of NFRs. The first categorization splits NFRs into four types namely functionally restrictive, additive restrictive, policy restrictive, and architecturally restrictive and the second categorization splits the NFRs into two types: operational and nonoperational. These categorizations would serve as an initial point for developing frameworks or methodologies for testing NFRs with aspects.