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

Introduce `EagerStringFormatting` check #1139

Open

Stephan202 wants to merge 2 commits into master from sschroevers/eager-string-formatting-check

+636 −19

Open

Introduce `EagerStringFormatting` check #1139

Tweaks

GitHub Actions / pitest completed Dec 28, 2024 in 0s

Pitest mutation testing feedback

Surviving mutants in this change: 2
Killed mutants in this change: 98

class	surviving	killed
🧟`tech.picnic.errorprone.bugpatterns.EagerStringFormatting`	1	58
🧟`tech.picnic.errorprone.bugpatterns.EagerStringFormatting$StringFormatExpression`	1	40

Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

Annotations

Check warning on line 132 in error-prone-contrib/src/main/java/tech/picnic/errorprone/bugpatterns/EagerStringFormatting.java

github-actions / pitest

A change can be made to line 132 without causing a test to fail

replaced return value with null for analyzeFormatStringContext (covered by 1 tests NullReturnValsMutator)

Check warning on line 248 in error-prone-contrib/src/main/java/tech/picnic/errorprone/bugpatterns/EagerStringFormatting.java

github-actions / pitest

A change can be made to a lambda on line 248 without causing a test to fail

replaced return value with null for 1st lambda in deriveFormatStringExpression (no tests cover this line NullReturnValsMutator)

View more details on GitHub Actions