Generate separated parametrized tests when we have different result types #652
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 improves parametrized test generation by generating separated tests in special cases that will be . There is a problem with different result types, in instance, if we have three classes with different fields in relation. It's impossible to choose
one
general execution. So, now in cases like this we generate separated parametrized tests.Fixes # (510)
Type of Change
How Has This Been Tested?
Automated Testing
Run utbot samples with enabled parametrized test generation.
Manual Scenario
Run
InstanceOfExampleTest
with enabled parametrized test generation. Verify that three separated parametrized tests for different result types are generated.