A methodology for controlling the size of a test suite
ACM Transactions on Software Engineering and Methodology (TOSEM)
Exploiting hardware performance counters with flow and context sensitive profiling
Proceedings of the ACM SIGPLAN 1997 conference on Programming language design and implementation
Approximation algorithms
Prioritizing Test Cases For Regression Testing
IEEE Transactions on Software Engineering
Towards the prioritization of regression test suites with data flow information
Proceedings of the 2005 ACM symposium on Applied computing
Call Stack Coverage for Test Suite Reduction
ICSM '05 Proceedings of the 21st IEEE International Conference on Software Maintenance
A concept analysis inspired greedy algorithm for test suite minimization
PASTE '05 Proceedings of the 6th ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering
Call Stack Coverage for GUI Test-Suite Reduction
ISSRE '06 Proceedings of the 17th International Symposium on Software Reliability Engineering
Search Algorithms for Regression Test Case Prioritization
IEEE Transactions on Software Engineering
An empirical study of incorporating cost into test suite reduction and prioritization
Proceedings of the 2009 ACM symposium on Applied Computing
Proceedings of the 2010 ACM Symposium on Applied Computing
Prioritizing test cases with string distances
Automated Software Engineering
Regression testing minimization, selection and prioritization: a survey
Software Testing, Verification & Reliability
Hi-index | 0.00 |
This paper presents a tool that (i) constructs tree-based models of a program's behavior during testing and (ii) employs these trees while reordering and reducing a test suite. Using either a dynamic call tree or a calling context tree, the test reduction component identifies a subset of the original tests that covers the same call tree paths. The prioritization technique reorders a test suite so that it covers the call tree paths more rapidly than the initial test ordering. In support of program and test suite understanding, the tool also visualizes the call trees and the coverage relationships. For a chosen case study application, the experimental results show that call tree construction only increases testing time by 13%. In comparison to the original test suite, the experiments show that (i) a prioritized suite achieves coverage much faster and (ii) a reduced test suite contains 45% fewer tests and consumes 82% less time