ACM Home Page
Please provide us with feedback. Feedback
Testing aspect-oriented programming Pointcut Descriptors
Full text PdfPdf (371 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: 33 - 38  
Year of Publication: 2006
ISBN:1-59593-415-4
Authors
Otávio Augusto Lazzarini Lemos  ICMC/USP - São Carlos, São Carlos-SP-Brasil
Fabiano Cutigi Ferrari  ICMC/USP - São Carlos, São Carlos-SP-Brasil
Paulo Cesar Masiero  ICMC/USP - São Carlos, São Carlos-SP-Brasil
Cristina Videira Lopes  University of California, Irvine
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 8,   Downloads (12 Months): 57,   Citation Count: 3
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1146374.1146380
What is a DOI?

ABSTRACT

Pointcut Descriptors (PCDs) are used to specify sets of program join points with a common property where additional behavior should be applied. If PCDs are wrongly formulated, faults are injected into the program, because additional behavior will be applied to unintended join points or will fail to be applied to intended join points. In this paper we classify the types of faults that can occur in PCDs -- in terms of selected join points -- and present a two-step strategy to: 1) help the tester identifying extra join points selected by PCDs; and 2) help the tester identifying neglected join points that should be selected by PCDs in the first place. We focus on the first step but provide motivating examples and directions for both.


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
R. T. Alexander, J. M. Bieman, and A. A. Andrews. Towards the systematic testing of aspect-oriented programs. Technical report, Department of Computer Science, Colorado State University, 2004.
 
2
R. A. DeMillo. Hints on test data selection: Help for the practicing programmer. IEEE Computer, 11(4):34--43, 1978.
 
3
 
4
G. Kiczales, J. Irwin, J. Lamping, J.-M. Loingtier, C. Lopes, C. Maeda, and A. Menhdhekar. Aspect-oriented programming. In M. Akşit and S. Matsuoka, editors, Proceedings of the European Conference on Object-Oriented Programming, volume 1241, pages 220--242, Berlin, Heidelberg, and New York, 1997. Springer-Verlag.
5
 
6
O. A. L. Lemos, J. C. Maldonado, and P. C. Masiero. Structural unit testing of AspectJ programs. In Proceedings of the 1stWorkshop on Testing Aspect Oriented Programs (WTAOP 2005) -- in conjunction with AOSD'2005, Chicago/IL, USA, 2005.
 
7
M. Mortensen and R. T. Alexander. An approach for adequate testing of AspectJ programs. In Proceedings of the 1stWorkshop on Testing Aspect Oriented Programs -- in conjunction with AOSD'2005, Chicago/IL, USA, 2005.
 
8
 
9
Object Mentor, Inc. JUnit, Testing Resources for Extreme Programming. Online, 2004. available at http://www.junit.org - last access: 03/25/2006.
10
11
 
12
The AspectJ Team. The AspectJ programming guide. Online, 2003. available at http://www.eclipse.org/aspectj/doc/released/progguide/index.html - last access: 03/25/2006.
 
13
14


Collaborative Colleagues:
Otávio Augusto Lazzarini Lemos: colleagues
Fabiano Cutigi Ferrari: colleagues
Paulo Cesar Masiero: colleagues
Cristina Videira Lopes: colleagues