Added configuration parameter to filter executed methods of target tests #438
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… challenge mutants
|
Thanks - sorry for the delay merging. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a pull request for issue #437
I tried to be as close as possible to the naming convention and coding style of the project. I also made sure that the tests are running and I created a few new tests for the change.
The goal of this change is to filter the executed tests of a test class. Hence, I added a new configuration parameter (includedTestMethods) for pitest in which you can put in a name (or names) of a test method and pitest only executes these methods for the targeted tests. The idea is to change the *TestUnitFinder classes. There, I implemented something similar to the Category-based filtering mechanism.