Automated flow graph-based testing of object-oriented software modules
Journal of Systems and Software - Special issue on object-oriented software
A Markov Chain Model for Statistical Software Testing
IEEE Transactions on Software Engineering
Slicing object-oriented software
Proceedings of the 18th international conference on Software engineering
ClassBench: a framework for automated class testing
Software—Practice & Experience
Computation of interprocedural control dependence
Proceedings of the 1998 ACM SIGSOFT international symposium on Software testing and analysis
A Unified Framework for Coupling Measurement in Object-Oriented Systems
IEEE Transactions on Software Engineering
Proceedings of the 2000 ACM SIGSOFT international symposium on Software testing and analysis
Incorporating varying test costs and fault severities into test case prioritization
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Prioritizing Test Cases For Regression Testing
IEEE Transactions on Software Engineering
Test Case Prioritization: A Family of Empirical Studies
IEEE Transactions on Software Engineering
Operational Profiles in Software-Reliability Engineering
IEEE Software
Slicing Objects Using System Dependence Graphs
ICSM '98 Proceedings of the International Conference on Software Maintenance
Dynamic Coupling Measurement for Object-Oriented Software
IEEE Transactions on Software Engineering
A brief survey of program slicing
ACM SIGSOFT Software Engineering Notes
Prioritize Code for Testing to Improve Code Coverage of Complex Software
ISSRE '05 Proceedings of the 16th IEEE International Symposium on Software Reliability Engineering
An efficient interprocedural dynamic slicing method
Journal of Systems and Software
Experiments with test case prioritization using relevant slices
Journal of Systems and Software
Optimizing preventive service of software products
IBM Journal of Research and Development
Code-based prioritization: a pre-testing effort to minimize post-release failures
Innovations in Systems and Software Engineering
Hi-index | 0.00 |
Even after thorough testing of a program, usually a few bugs still remain. These residual bugs are randomly distributed through out the code. It is observed that bugs in some parts of a program can cause more frequent and more severe failures compared to those in other parts. So, it is possible to prioritize the program elements at the time of testing according to their potential to cause failures. Based on this idea, we have proposed a metric to compute the influence of an object in an object-oriented program. Influence of an element indicates the potential of the element to cause failures. The intensity with which each element is tested is proportionate to its influence value. We have conducted experiments to compare our scheme with related schemes. The results establish that the failure rate can indeed be minimized using our scheme when the software is executed for some duration after the completion of testing phase. Our proposed metric can be useful in applications such as coding, debugging, test case design and maintenance etc.