Uh oh!
There was an error while loading. Please reload this page.
Add mocking listener in plugin - #1604
Merged
Merged
Conversation
EgorkaKulikov
approved these changes
Dec 30, 2022
tamarinvs19 pushed a commit
that referenced
this pull request
Jan 9, 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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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
Before the PR we listened to force mocking occurrence events in parameterized test generation only in utbot-samples runs.
This PR adapts the feature for plugin.
Second attempt of pull845
Fixes # (844)
Type of Change
How Has This Been Tested?
Regression and integration tests
Automated Testing
utbot-samples.
Manual Scenario
Generate a parameterized test for a method vertexSum from RecursionTest in plugin. Verify that there is only one data provider (one processed execution without Random() mock) out of two.