Software unit test coverage and adequacy
ACM Computing Surveys (CSUR)
ECOOP '01 Proceedings of the 15th European Conference on Object-Oriented Programming
Data-Flow-Based Unit Testing of Aspect-Oriented Programs
COMPSAC '03 Proceedings of the 27th Annual International Conference on Computer Software and Applications
The Art of Software Testing
A classification system and analysis for aspect-oriented programs
Proceedings of the 12th ACM SIGSOFT twelfth international symposium on Foundations of software engineering
Aspect-oriented programming and modular reasoning
Proceedings of the 27th international conference on Software engineering
Information hiding interfaces for aspect-oriented design
Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering
Generation of test requirements from aspectual use cases
Proceedings of the 3rd workshop on Testing aspect-oriented programs
Control and data flow structural testing criteria for aspect-oriented programs
Journal of Systems and Software
A test driven approach for aspectualizing legacy software using mock systems
Information and Software Technology
Science of Computer Programming
Information Sciences: an International Journal
A pointcut-based coverage analysis approach for aspect-oriented programs
Information Sciences: an International Journal
On generating mutants for AspectJ programs
Information and Software Technology
Journal of Systems and Software
The crosscutting impact of the AOSD Brazilian research community
Journal of Systems and Software
A critical review of various testing techniques in aspect-oriented software systems
ACM SIGSOFT Software Engineering Notes
Hi-index | 0.02 |
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.