Remove VS Code Jupyter integration tests#3245
Open
swernli wants to merge 2 commits into
Open
Conversation
These tests have become more flaky over time and rely on UX elements we don't have control over (specifically the VS Code + Jupyter extension activation and cell processing). We get good anecodotal reports on notebook usability, have other automated Jupyter notebook tests to verify functionality, and see the user experience ourselves when running/editing notebooks for samples and such, so it seems safe to remove the flaky test cases. Fixes #3206
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
These tests have become more flaky over time and rely on UX elements we don't have control over (specifically the VS Code + Jupyter extension activation and cell processing). We get good anecodotal reports on notebook usability, have other automated Jupyter notebook tests to verify functionality, and see the user experience ourselves when running/editing notebooks for samples and such, so it seems safe to remove the flaky test cases. Fixes #3206