Software testing techniques (2nd ed.)
Software testing techniques (2nd ed.)
Incremental testing of object-oriented class structures
ICSE '92 Proceedings of the 14th international conference on Software engineering
Using genetic algorithms and coupling measures to devise optimal integration test orders
SEKE '02 Proceedings of the 14th international conference on Software engineering and knowledge engineering
Test Order for Inter-Class Integration Testing of Object-Oriented Software
COMPSAC '97 Proceedings of the 21st International Computer Software and Applications Conference
An Investigation of Graph-Based Class Integration Test Order Strategies
IEEE Transactions on Software Engineering
A Parameterized Cost Model to Order Classes for Class-based Testing of C ++ Applications
ISSRE '03 Proceedings of the 14th International Symposium on Software Reliability Engineering
A Test Strategy for Object-Oriented Programs
COMPSAC '95 Proceedings of the 19th International Computer Software and Applications Conference
Minimizing stub creation during integration test of aspect-oriented programs
Proceedings of the 3rd workshop on Testing aspect-oriented programs
Quantitatively measuring object-oriented couplings
Software Quality Control
A Pareto ant colony algorithm applied to the class integration and test order problem
ICTSS'10 Proceedings of the 22nd IFIP WG 6.1 international conference on Testing software and systems
Establishing integration test orders of classes with several coupling measures
Proceedings of the 13th annual conference on Genetic and evolutionary computation
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 |
During component-based and object-oriented software development, software classes exhibit relationships that complicate integration, including method calls, inheritance, and aggregation. When classes are integrated and tested, an order of integration must be established. The difficulty arises when cyclic dependencies exist - the functionality that is used by the first class to be tested must be mimicked by creating "stubs" (sometimes called "mocks"), an expensive and error-prone operation. This problem is generally called the class integration and test order (CITO) problem, and solutions must be fully automated for integration and testing to proceed smoothly and efficiently. This paper describes new techniques and algorithms to solve the CITO problem. New results include improved edge weights that are derived from quantitative coupling measures to more precisely model the cost of stubbing, and the use of weights on nodes, allowing more information to be used. Also, a new algorithm for computing the integration and test orders is presented. The technique is compared with an existing approach with positive results.