26455e9113
* Build breaks 1 * Build breaks * Build breaks * Build breaks * More build breaks * Build breaks (#2512) * Runtime breaks * Build breaks * Fix dialog location break * Update typescript * Fix ASAR break issue * Unit test breaks * Update distro * Fix breaks in ADO builds (#2513) * Bump to node 16 * Fix hygiene errors * Bump distro * Remove reference to node type * Delete vscode specific extension * Bump to node 16 in CI yaml * Skip integration tests in CI builds (while fixing) * yarn.lock update * Bump moment dependency in remote yarn * Fix drop-down chevron style * Bump to node 16 * Remove playwrite from ci.yaml * Skip building build scripts in hygine check
Unit Tests
Run (inside Electron)
./scripts/test.[sh|bat]
All unit tests are run inside a electron-browser environment which access to DOM and Nodejs api. This is the closest to the environment in which VS Code itself ships. Notes:
- use the
--debugto see an electron window with dev tools which allows for debugging - to run only a subset of tests use the
--runor--globoptions - use
yarn 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)
yarn 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 yarn
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
Run (with node)
yarn run mocha --ui tdd --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.bat --coverage
NOTE: When running locally the coverage will be generated for the .js files because by default the sourcemaps
are inlined. To fix this set the environment variable SQL_NO_INLINE_SOURCEMAP to 1, re-run the
compile/watch task and then re-run the test script with coverage enabled.