Skip to content

fix(build): exclude config classes from PIT mutation testing #296

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
arunderwood merged 1 commit into from
Jan 6, 2026
Merged

fix(build): exclude config classes from PIT mutation testing #296

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions build.gradle.kts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -315,6 +315,15 @@ configure<io.github.surpsg.deltacoverage.gradle.DeltaCoverageConfiguration> {
pitest {
targetClasses = setOf("io.nextskip.*")
targetTests = setOf("io.nextskip.*")
// Exclude infrastructure/configuration classes from mutation testing.
// These have void method calls (e.g., setCorePoolSize) that configure Spring beans
// but don't affect observable test behavior - tests verify the app loads, not config values.
excludedClasses = setOf(
"io.nextskip.common.config.AsyncConfig",
"io.nextskip.common.config.ClockConfig",
"io.nextskip.common.config.ResilienceConfig",
"io.nextskip.common.scheduler.DbSchedulerConfig"
)
mutators = setOf("DEFAULTS")
// Dynamic thread allocation: use 75% of available cores, minimum 2
val availableCores = Runtime.getRuntime().availableProcessors()
Expand Down