APTE

Subscribe (Full Service)


	Search: The ACM Digital Library The Guide

	Feedback

APTE: automated pointcut testing for AspectJ programs

Full text

Pdf (252 KB)

Source

International Symposium on Software Testing and Analysis archive
Proceedings of the 2nd workshop on Testing aspect-oriented programs table of contents

Portland, Maine

Pages: 27 - 32

Year of Publication: 2006

ISBN:1-59593-415-4

Authors

Prasanth Anbalagan	North Carolina State University, Raleigh, NC
Tao Xie	North Carolina State University, Raleigh, NC

Publisher

ACM New York, NY, USA

Bibliometrics

Downloads (6 Weeks): 3, Downloads (12 Months): 26, Citation Count: 4

Additional Information:

abstract references cited by index terms collaborative colleagues

Tools and Actions:	Request Permissions Review this Article Save this Article to a Binder Display Formats: BibTeX EndNote ACM Ref

DOI Bookmark:	Use this link to bookmark this Article: http://doi.acm.org/10.1145/1146374.1146379 What is a DOI?

ABSTRACT

Aspect-Oriented Programming (AOP) has been proposed as a methodology that provides new modularization of software systems by allowing encapsulation of cross-cutting concerns. AspectJ, an aspect-oriented programming language, provides two major constructs: advice and pointcuts. The scope of pointcuts spans across various objects instantiated from the classes. With the increase in the number of objects, classes, and integration of source code, it is likely that a developer writes a pointcut that does not serve its intended purpose. Therefore, there is a need to test pointcuts for validating the correctness of their expressions.In this paper, we propose APTE, an automated framework that tests pointcuts in AspectJ programs with the help of AJTE, an existing unit-testing framework without weaving. Our new APTE framework identifies joinpoints that satisfy a pointcut expression and a set of boundary joinpoints, which are events that do not satisfy a pointcut expression but are close to the matched joinpoints. The boundary joinpoints are identified as those unmatched join-point candidates whose distance from the matched joinpoints are less than a predefined threshold value. A developer could inspect these matched joinpoints and boundary joinpoints for correctness of the pointcuts.

REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

	1	Ken Arnold , James Gosling , David Holmes, The Java Programming Language, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 2000
	2	Robert V. Binder, Testing object-oriented systems: models, patterns, and tools, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
	3	M. Dahm and J. van Zyl. Byte Code Engineering Library, April 2003. http://jakarta.apache.org/bcel/.
	4	Eclipse. AspectJ compiler 1.5, May 2005. http://eclipse.org/aspectj/.
	5	R. E. Filman and T. Elrad. Aspect Oriented Software Development. Addison-Wesley Publishing Co., Inc.,, 2005.
	6	A. Kellens, K. Gybels, J. Brichau, and K. Mens. A model-driven pointcut language for more robust pointcuts. In Proc. Workshop on Software Engineering Properties of Languages for Aspect Technology (SPLAT), March 2006.
	7	C. Koppen and M. Stoerzer. PCDiff: Attacking the fragile pointcut problem. In Proc. 1st European Interactive Workshop on Aspects in Software (EIWAS), July 2004.
	8	Tim Lindholm , Frank Yellin, Java Virtual Machine Specification, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1999
	9	C. V. Lopes and T. Ngo. Unit testing aspectual behavior. In Proc. AOSD 05 Workshop on Testing Aspect-Oriented Programs, March 2005.
	10	Russell Miles, AspectJ Cookbook, O'Reilly Media, Inc., 2004
	11	M. Mortensen and R. T. Alexander. An approach for adequate testing of AspectJ programs. In Proc. AOSD 05 Workshop on Testing Aspect-Oriented Programs, March 2005.
	12	Maximilian Stoerzer , Juergen Graf, Using Pointcut Delta Analysis to Support Evolution of Aspect-Oriented Software, Proceedings of the 21st IEEE International Conference on Software Maintenance (ICSM'05), p.653-656, September 25-30, 2005 [doi>10.1109/ICSM.2005.99]
	13	Sun Microsystems. Java Reflection API. Online manual, 2001.
	14	Sun Microsystems. Java 2 platform standard edition v1.4.2 API specification, 2003. http://java.sun.com/j2se/1.4.2/docs/api/.
	15	The AspectJ Team. The AspectJ programming guide. Online manual, 2003.
	16	Tao Xie , Jianjun Zhao, A framework and tool supports for generating test inputs of AspectJ programs, Proceedings of the 5th international conference on Aspect-oriented software development, March 20-24, 2006, Bonn, Germany [doi>10.1145/1119655.1119681]
	17	Y. Yamazaki, K. Sakurai, S. Matsuura, H. Masuhara, H. Hashiura, and S. Komiya. A unit testing framework for aspects without weaving. In Proc. 1st Workshop on Testing Aspect-Oriented Programs (WTAOP), March 2005.

CITED BY 4

	Tao Xie , Jianjun Zhao, Perspectives on automated testing of aspect-oriented programs, Proceedings of the 3rd workshop on Testing aspect-oriented programs, p.7-12, March 12-13, 2007, Vancouver, British Columbia, Canada
	Dianxiang Xu , Xudong He, Generation of test requirements from aspectual use cases, Proceedings of the 3rd workshop on Testing aspect-oriented programs, p.17-22, March 12-13, 2007, Vancouver, British Columbia, Canada
	Lingdong Ye , Kris De Volder, Tool support for understanding and diagnosing pointcut expressions, Proceedings of the 7th international conference on Aspect-oriented software development, March 31-April 04, 2008, Brussels, Belgium
	Prasanth Anbalagan , Tao Xie, Automated Inference of Pointcuts in Aspect-Oriented Refactoring, Proceedings of the 29th International Conference on Software Engineering, p.127-136, May 20-26, 2007