Generate standard tests for symbolic executions with mocking in parametrized mode #1252
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
This PR adds more coverage by generating previously ignored test cases. Before, we skipped executions with mocking when generating parameterized tests. Now, we generate standard test in these cases.
This behavior is similar to our way of processing fuzzer executions (that may also contain force-mocking) in parametrized mode.
Fixes # (1231)
Type of Change
How Has This Been Tested?
Automated Testing
UTBot samples.
Manual Scenario
Run MockFinalClassTest for useFinalClassMethod() method. Verify that now there are three generated tests instead of two (as it was when we excluded symbolic executions with mocking in them).