You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the sandbox testing, make sure to configure "window.experimental.useSandbox": true and restart. You can check devtools for when sandbox is really enabled:
This is an exploratory test plan item while running with sandbox enabled.
Note: keep the setting also enabled in your selfhost build for broader coverage 🚀
Functionality
open files and folders and do basic editing, including language features and watch the Developer Tools console for suspicious errors or general issues while doing so
go through all our views and panels and check they open and work for the intent they are made for
also try non standard editors like a notebook and a custom editor for they work fine
open multiple windows, close some and verify you always have 1 extension host process per window (use the Help > Open Process Explorer to find the processes)
develop a simple hello world extension (yo code) and verify debugging and extension tests work
watch out for actions that seem slow or cause spinners to appear, overall VSCode should not run any noticeably slower when sandbox is enabled but it will have a slight performance impact because of process isolation
briefly test that screen reader works and announces the focused element properly (documentation)
macOS/Windows: run VSCode as admin with a fresh --user-data-dir and verify the window opens and generally it works without crashes
Development
use Developer Tools for setting a breakpoint and verify you can debug VSCode insiders as before
similar, run a performance trace and verify it works and it can be displayed in Developer Tols
The text was updated successfully, but these errors were encountered:
Amazing work! I went through the test plan and have also been running with this setting enabled for a few days. Works great
One question: when I tried to profile my extensions using the running extensions view, I saw a notification that a restart was required. Is this new? I feel like I have not seen it before enabling the sandbox flag
Refs: #154006
Complexity: 5
Create Issue
For the sandbox testing, make sure to configure
"window.experimental.useSandbox": true
and restart. You can check devtools for when sandbox is really enabled:This is an exploratory test plan item while running with sandbox enabled.
Note: keep the setting also enabled in your selfhost build for broader coverage 🚀
Functionality
yo code
) and verify debugging and extension tests work--user-data-dir
and verify the window opens and generally it works without crashesDevelopment
The text was updated successfully, but these errors were encountered: