Given two test cases, one larger and one smaller, the smaller test case is preferred for many
purposes. A smaller test case usually runs faster, is easier to understand, and is more …

Most test suite reduction techniques aim to select, from a given test suite, a minimal
representative subset of test cases that retains the same code coverage as the suite …

As a software system evolves, its test suite can accumulate redundancies over time. Test
minimization aims at removing redundant test cases. However, current techniques remove …

Test suite reduction seeks to reduce the number of test cases in a test suite while retaining a
high percentage of the original suite's fault detection effectiveness. Most approaches to this …

Regression testing is an important activity that can be expensive (eg, for large test suites).
Test suite reduction approaches speed up regression testing by removing redundant test …

Code coverage is the dominant criterion in test-suite reduction. Typically, most test-suite
reduction techniques repeatedly remove tests covering code that has been covered by other …

Software testing is a critical part of software development. As new test cases are generated
over time due to software modifications, test suite sizes may grow significantly. Because of …

Test suite minimization techniques attempt to reduce the cost of saving and reusing tests
during software maintenance, by eliminating redundant tests from test suites. A potential …

Background. Regression testing is conducted after changes are made to a system in order to
ensure that these changes did not alter its expected behavior. The problem with regression …

As a software project evolves over time, the associated test suite usually grows with it. If test
suites are not carefully maintained, this can easily result in massive test execution duration …