* ci: parallelize integration and smoke test shards
Run Agent Host E2E beside the remaining Electron integration tests, split Electron smoke coverage into core and chat shards, and isolate the macOS proxy scenarios from the main smoke critical path.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* ci: reduce test runner startup overhead
Skip redundant prelaunch work on prepared CI runners, avoid Browser-only Copilot compilation, disable login-shell probing on test servers, and reduce Browser unit console output while preserving JUnit results.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* ci: reuse prepared runners for integration tests
Run Agent Host E2E concurrently inside the existing Electron integration jobs and recombine core and chat smoke coverage, eliminating repeated checkout, dependency restore, transpilation, and Electron setup. Keep only the macOS network proxy smoke job isolated because it changes global network state.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Revert "ci: parallelize integration and smoke test shards"
This reverts commit 56126088db.
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Unit Tests
Run (inside Electron)
./scripts/test.[sh|bat]
All unit tests are run inside a Electron renderer environment which access to DOM and Nodejs api. This is the closest to the environment in which VS Code itself ships. Notes:
- use the
--devto see an electron window with dev tools which allows for debugging - to run only a subset of tests use the
--runor--globoptions - use
npm run watchto automatically compile changes
For instance, ./scripts/test.sh --debug --glob **/extHost*.test.js runs all tests from extHost-files and enables you to debug them.
Run (inside browser)
npm run test-browser -- --browser webkit --browser chromium
Unit tests from layers common and browser are run inside chromium, webkit, and (soon'ish) firefox (using playwright). This complements our electron-based unit test runner and adds more coverage of supported platforms. Notes:
- these tests are part of the continuous build, that means you might have test failures that only happen with webkit on windows or chromium on linux
- you can run these tests locally via
npm run test-browser -- --browser chromium --browser webkit - to debug, open
<vscode>/test/unit/browser/renderer.htmlinside a browser and use the?m=<amd_module>-query to specify what AMD module to load, e.gfile:///Users/jrieken/Code/vscode/test/unit/browser/renderer.html?m=vs/base/test/common/strings.testruns all tests fromstrings.test.ts - to run only a subset of tests use the
--runor--globoptions
Note: you can enable verbose logging of playwright library by setting a DEBUG environment variable before running the tests (https://playwright.dev/docs/debug#verbose-api-logs)
Run (with node)
npm run test-node -- --run src/vs/editor/test/browser/controller/cursor.test.ts
Coverage
The following command will create a coverage folder in the .build folder at the root of the workspace:
OS X and Linux
./scripts/test.sh --coverage
Windows
scripts\test --coverage