-
Notifications
You must be signed in to change notification settings - Fork 293
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
couple of settings tweaks from VS Code for our tests #6279
Conversation
I found this related VS Code issue, so giving a settings recommendation from there a shot. |
@@ -26,5 +26,6 @@ | |||
// We don't want jupyter to start when testing (DS functionality or anything else). | |||
"jupyter.disableJupyterAutoStart": true, | |||
"jupyter.logging.level": "debug", | |||
"python.logging.level": "debug" | |||
"python.logging.level": "debug", | |||
"webview.experimental.useIframes": true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was the vscode recommended setting change. They use it in their smoke tests.
microsoft/vscode#125733
@@ -111,6 +111,8 @@ async function start() { | |||
extensionTestsPath: path.join(EXTENSION_ROOT_DIR_FOR_TESTS, 'out', 'test', 'index'), | |||
launchArgs: baseLaunchArgs | |||
.concat([workspacePath]) | |||
.concat(['--skip-welcome']) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also saw these in their test files. Felt like they might be good for test stability so I added them as well.
For #6234
package-lock.json
has been regenerated by runningnpm install
(if dependencies have changed).