Introduce Spring codegen instances and collect types of mocked class variables#1791
Merged
Conversation
Damtev
requested changes
Feb 14, 2023
ea309c6 to
ab3daed
Compare
Damtev
approved these changes
Feb 14, 2023
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Spring unit tests require to inject Mockito mocks in different way than pure Java tests.
To do it, we require per-class variables for all instances whose methods will be mocked in tests.
To collect per-class variables, we traverse all UtModels in test sets to find mocked classes.
Some refactoring of Cg-instances introduced: we would like to minimize regressions in standard codegen process.
How to test
Should not be tested separately, just some preparation logic for future Spring codegen and rendering.
Logic is temporarly disabled in main:
isSpringClass=false.Self-check list