Pitest mutating methods called from static blocks
See original GitHub issuePitest mutates methods called from static initializer blocks with nested depth > 1.
✅ Pit is not mutating code present in static blocks.
✅ It is also not mutating private method called from static block i.e. fillShortToFullModuleNamesMap
❌ But the methods called from this private methods are mutated by pit, these methods are only called from
fillShortToFullModuleNamesMap
but still they are mutated, see fillChecksFromAnnotationPackage
Issue Analytics
- State:
- Created a year ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Mutation operators - PIT Mutation Testing
Pitest will filter out equivalent mutations to methods that are already hard coded to return 0. Optional Mutators. Constructor Call Mutator (CONSTRUCTOR_CALLS).
Read more >FAQ - PIT Mutation Testing
Mitigation. Pitest tries to avoid mutating static initializer code. It will not create mutants in. static initializers; private methods called only from static...
Read more >Mutation testing systems for Java compared
Several mutation testing systems for Java exist, this page in an attempt to objectively categorise and compare the way in which they are...
Read more >Command line quick start - PIT Mutation Testing
The command-line tool supports two methods of supplying the classpath to be mutated. By default the launch classpath will be used.
Read more >Downloads - PIT Mutation Testing
These are old releases from before pitest was migrated to github. ... new remove conditionals mutator; support for mutating static initializers with TestNG ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
released in 1.9.4
Should be fixed by #1069