Allow different field and getter method naming standards
This check has been archived and is scheduled for deletion.
Learn more about checks retention
GitHub Actions / pitest
completed
Jun 29, 2023 in 1s
Pitest mutation testing feedback
- Surviving mutants in this change: 2
- Killed mutants in this change: 4
| class | surviving | killed |
|---|---|---|
nl.jqno.equalsverifier.ConfiguredEqualsVerifier |
1 | 0 |
nl.jqno.equalsverifier.api.MultipleTypeEqualsVerifierApi |
1 | 0 |
nl.jqno.equalsverifier.api.SingleTypeEqualsVerifierApi |
0 | 1 |
nl.jqno.equalsverifier.internal.util.Configuration |
0 | 3 |
Mutation testing report generated by PITest - https://pitest.org - if there are surviving mutants, please check the line comments under 'Files changed', or the full report under the 'CI / pitest' check below this comment.
Annotations
github-actions / pitest
A change can be made to line 104 without causing a test to fail
replaced return value with null for withFieldnameToGetterConverter (0 tests run NullReturnValsMutator)
github-actions / pitest
A change can be made to line 80 without causing a test to fail
replaced return value with null for withFieldnameToGetterConverter (0 tests run NullReturnValsMutator)
Loading