allow multiple test engines #900
Merged
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
szpak
added a commit
to szpak/kotest
that referenced
this pull request
Mar 26, 2022
Starting with PIT 1.6.7 it is just enough to have kotest-extensions-pitest on (test) classpath Over more that parameter is already deprecated and "marked for deletion". See: hcoles/pitest#900 szpak/gradle-pitest-plugin#277
sksamuel
pushed a commit
to kotest/kotest
that referenced
this pull request
Mar 27, 2022
Starting with PIT 1.6.7 it is just enough to have kotest-extensions-pitest on (test) classpath Over more that parameter is already deprecated and "marked for deletion". See: hcoles/pitest#900 szpak/gradle-pitest-plugin#277
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.
Adds support for multiple pitest test plugins. Pitest will attempt to use any testengine placed on its classpath, trying them in order of precedence. A test plugin must either completely handle a test class, or not handle it at all.
This enables support for legacy projects that mix Junit and TestNG.
As a result of this change the 'testPlugin' parameter is now redundant, but has been retained for this release.