Mock VS Code before importing modules in scheduled cli output test #1737
Conversation
This file contains 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
mattseddon
force-pushed
the
fix-scheduled-cli-test
branch
from
3185ab9 to
6bb5209
Compare
mattseddon
commented
May 19, 2022
| import { setupVenv } from '../../python' | ||
| import { runMocha } from '../util/mocha' | ||
|
|
||
| const importModulesAfterMockingVsCode = () => { |
There was a problem hiding this comment.
[F] This pattern should prevent this from happening again in the future.
sroy3
approved these changes
May 19, 2022
rogermparent
approved these changes
May 19, 2022
|
Code Climate has analyzed commit aaea5a4 and detected 0 issues on this pull request. The test coverage on the diff in this pull request is 100.0% (85% is the threshold). This pull request will bring the total coverage in the repository to 96.7% (0.0% change). View more on Code Climate. |
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.
Recent failure caused by importing of vscode into processExecution (#1731)
Tests now pass locally.