Skip to content

Commit

Permalink
Adjust PIT gradle plugin configuration (#2903)
Browse files Browse the repository at this point in the history
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
  • Loading branch information
szpak committed Mar 27, 2022
1 parent 999d1c1 commit 3082dc9
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion documentation/docs/extensions/pitest.md
Expand Up @@ -22,7 +22,7 @@ After doing that, we need to inform Pitest that we're going to use `Kotest` as a
```kotlin
// Assuming that you have already configured the Gradle/Maven extension
configure<PitestPluginExtension> {
testPlugin.set("Kotest") // <-- Telling Pitest that we're using Kotest
// testPlugin.set("Kotest") // needed only with old PIT <1.6.7, otherwise having kotest-extensions-pitest on classpath is enough
targetClasses.set(listOf("my.company.package.*"))
}
```
Expand Down

0 comments on commit 3082dc9

Please sign in to comment.