search

stryker-mutator / editor-plugins

A monorepo for editor plugins to help with mutation testing.
Apache License 2.0
0 stars 0 forks source link

Add support for testing specific mutants #10

Open Aimless321 opened 3 hours ago

Aimless321 commented 3 hours ago

Currently, it is possible to specify which blocks of code need to be tested using mutation ranges, but there's no way to specify which individual mutants within those blocks should be tested.

Use case

In the Stryker Cloud Orchestrator, a mutation test run is split into tasks, where each task contains a set of mutants to be tested. These tasks are optimized based on test coverage to allow multiple mutants to be tested in the same task as long as there is no overlap in their test coverage.

To support this use case, it would be helpful to have a mechanism to specify exactly which mutants should be tested, rather than testing all mutants within a given code block.

Would it be possible to do this based on the mutatorName in combination with the current ranges?

rouke-broersma commented 3 hours ago

~In our use case mutant IDs are stable - for this specific use case, so we could also simply optionally allow mutant ID in MSP.~

We could optionally allow mutant ID, to be used if the specific MSP server supports guaranteed stable mutant IDs when there are not changed to source code.