Implementing distribution and persistence aspects with aspectJ
OOPSLA '02 Proceedings of the 17th ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Proceedings of the 2nd international conference on Aspect-oriented software development
AOP: Does It Make Sense? The Case of Concurrency and Failures
ECOOP '02 Proceedings of the 16th European Conference on Object-Oriented Programming
An Investigation of Graph-Based Class Integration Test Order Strategies
IEEE Transactions on Software Engineering
Coupling-based class integration and test order
Proceedings of the 2006 international workshop on Automation of software test
Integration test of classes and aspects with a multi-evolutionary and coupling-based approach
SSBSE'11 Proceedings of the Third international conference on Search based software engineering
| Hi-index | 0.00 |
A problem related to the integration test of Object-Oriented programs is the order in which classes are integrated and tested. This problems also appears in Aspect-Oriented programs. The incremental integration strategy, which suggests that classes are tested first and then integrated to the aspects, is often proposed as the more adequate strategy to integrate classes and aspects. This work presents a study about ordering classes and aspects in Aspect-Oriented programming to minimize the number of stubs in integration test. A dependency type model among classes and aspects is defined considering the syntax constructions and the semantics of AspectJ. An algorithm for class ordering is adapted and applied to an AOP program and the result obtained is analyzed and discussed, showing that a more refined strategy than the plain incremental approach is better in several situations.