You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
Passing only the file and location of the BlockStatement mutant, would also cause the 2nd mutant to be tested.
Perhaps it would make more sense to treat the locations passed to the mutationTest method as exact locations, instead of an area to search for mutants. Combined with the mutatorName i think that would be a consistent way of specifying a single mutant?
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?The text was updated successfully, but these errors were encountered: