Improve detection of NPEs caused by this instance fields being null in Spring unit tests #2617
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Description
Fixes #2589 (desired NPE test is generated by fuzzer, because symbolic engine has troubles dealing with
getClass() == o.getClass()condition.To make fuzzer able to generate
Objectof typeOrderspecialJavaLangObjectValueProviderwas added that tries to useclassUnderTestwheneverjava.lang.Objectis needed (plainnew Object()can still be used wherejava.lang.Objectis needed).In case class under test has some hard to pass validation inside of the constructor and fuzzer is asked to create multiple
java.lang.Objects,RemovingConstructFailsUtExecutionInstrumentationwas used in all Spring tests (in short, it detects impossible to create due to exceptions thrown by constructor models instateBeforeand replaces them withUtNullModels, making it easier for fuzzer to find "creatable" input and actually call method under test).Finally,
InjectMocksValueProviderwas made to respectNonNullSpeculator(previously fuzzer considered all fields to be non-null).How to test
Manual tests
NPE unit be generated by fuzzer for
Order.equals()fromspring-boot-testingproject.Generate unit tests for the following classes individually with fuzzer only and with engine only, each of them should generate NPE tests for methods marked with "NPE expected" and no NPE tests for methods marked with "no NPE expected".
Self-check list