test-deduplicator

You can reduce CI execution time by analyzing test coverage and mutation testing results to identify and remove redundant tests. This deduplication process eliminates tests that cover the same code or assert the same behavior, significantly shrinking the test suite.

Test suite deduplication is the process of identifying and removing redundant tests by analyzing per-test coverage data and mutation testing results. It detects tests that kill the same mutants or assert identical behavior, ensuring bug-killing capabilities remain intact after deletion.

Yes, mutation testing integration verifies behavioral equivalence by checking that deleting a specific test does not remove critical bug-killing capabilities. This ensures that removing redundant tests maintains the same defect detection quality across the codebase.

The best way to consolidate similar tests is by analyzing code structure and test coverage data to identify opportunities for parametrization. This process detects tests asserting comparable behaviors and provides actionable insights to merge them into a single parameterized test.

Removing redundant tests does not sacrifice code coverage when leveraging per-test coverage data to find subsumed tests. By ensuring that remaining tests still provide full coverage and kill the same mutants, the optimization process maintains quality while reducing runtime costs.

You should optimize your test suite for redundancy when execution takes too long or CI costs are escalating due to a large number of tests. Analyzing test coverage and code structure at this stage identifies bloated areas suitable for deduplication and parametrization.