Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve verification that static mocking is configured #1091

Merged
merged 2 commits into from
Oct 5, 2022

Conversation

EgorkaKulikov
Copy link
Collaborator

Description

Current implementation of searching that static mocking is configured has a problem that we firstly obtain all file names from the content entry and only after that verify that a required name is present. It will lead us to problems if there are millions of files in the content entry.
Implementation was improved in accordance with lazy practices.

Type of Change

  • Refactoring (typos and non-functional changes)

How Has This Been Tested?

Manual Scenario

Verify that we do not create tests with static mocking if there is no special file in any of test source root resource folders.

@EgorkaKulikov EgorkaKulikov merged commit c34324a into main Oct 5, 2022
@EgorkaKulikov EgorkaKulikov deleted the egor/static_mocks_file_search branch October 5, 2022 11:49
@alisevych alisevych added this to the 2022.10.1 Release milestone Oct 7, 2022
AbdullinAM pushed a commit to AbdullinAM/UTBotJava that referenced this pull request Oct 17, 2022
)

* Improve verification that static mocking is configured

* Wrap file reading with try/catch
AbdullinAM pushed a commit to AbdullinAM/UTBotJava that referenced this pull request Oct 17, 2022
)

* Improve verification that static mocking is configured

* Wrap file reading with try/catch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants