Regression testing in an industrial environment
Communications of the ACM
A static analyzer for finding dynamic programming errors
Software—Practice & Experience
Prioritizing Test Cases For Regression Testing
IEEE Transactions on Software Engineering
Test Case Prioritization: A Family of Empirical Studies
IEEE Transactions on Software Engineering
Managing The Testing Process
Inside Microsoft Windows 2000
Effectively prioritizing tests in development environment
ISSTA '02 Proceedings of the 2002 ACM SIGSOFT international symposium on Software testing and analysis
Industrial-Strength Management Strategies
IEEE Software
Testing Component-Based Software: A Cautionary Tale
IEEE Software
UML-Based Integration Testing for Component-Based Software
ICCBSS '03 Proceedings of the Second International Conference on COTS-Based Software Systems
An Integrated Testing Technique for Component-Based Software
AICCSA '01 Proceedings of the ACS/IEEE International Conference on Computer Systems and Applications
Techniques for Testing Component-Based Software
ICECCS '01 Proceedings of the Seventh International Conference on Engineering of Complex Computer Systems
The When-Who-How analysis of defects for improving the quality control process
Journal of Systems and Software
Unit Testing of Software Components with Inter-component Dependencies
CBSE '09 Proceedings of the 12th International Symposium on Component-Based Software Engineering
| Hi-index | 0.00 |
Most large software systems are architected as component-based systems. In such systems, components are developed and tested separately. As components cooperate for providing services, testing of a component also reveals defects in other components. In this paper we study the role testing of other components plays in finding defects in a component by analyzing defect data of an earlier version of Windows. Our analysis shows that testing of other components often is the largest source of finding defects in a component. The analysis also shows that though many components reveal defects in a component, often a small set of components – the Test Buddies – exists whose testing reveals the vast majority of the defects found by testing other components. The Test Buddies of a component are those with a heavy interaction with the component and represent the high priority customers for testing. The Test Buddy information for a system can be determined by the test data of an earlier release, and then can be used in different ways to improve the testing.