mirror of
https://github.com/microsoft/vscode.git
synced 2026-04-20 00:04:14 +08:00
73643c60a6
* Bump electron@4.0.0-beta.9 * electron 4 - temporarily warn about exploration change * update to Electron 4.0.0 stable * remove electron 4 notification * bump to electron@4.0.1 * electron 4: adopt format change of "version" file * build - set to use exploration image * Revert "build - set to use exploration image" This reverts commit 1bb280fc5e96a4cf5a5acf1fc4f77e8a864ed5c6. * electron@4.0.2 * fix electron.d.ts * update distro * bump electron@4.0.4 * debt - adopt new process.getProcessMemoryInfo() * update electron@4.0.5 * electron@4.0.6 * electron 4.0.x - remove Linux 32bit build * electron@4.0.7 * electron - update to 4.1.2 * bump electron@4.1.4 * update build (remove Linux32) * electron@4.1.5 * electron 4 - remove linux 32bit warning * Remove more 32-bit Linux build stuff Fixes #66271 * electron@4.2.0 * electron@4.2.1 * electron@4.2.2 * electron@4.2.3 * Revert "electron@4.2.3" This reverts commit ae375ef764a13ccffbec1fdef15926d814d90872. * Revert "Revert "electron@4.2.3"" This reverts commit 513581ebc59bfa1af574ea40d61974492b0db64f.
Tests
Run
The best way to run the Code tests is from the terminal. To make development changes to unit tests you need to be running yarn run watch. See Development Workflow for more details. From the vscode folder run:
OS X and Linux
./scripts/test.sh
Windows
scripts\test
Debug
To debug tests use --debug when running the test script. Also, the set of tests can be reduced with the --run and --runGlob flags. Both require a file path/pattern. Like so:
./scripts/test.sh --debug --runGrep **/extHost*.test.js
Coverage
The following command will create a coverage folder at the root of the workspace:
OS X and Linux
./scripts/test.sh --coverage
Windows
scripts\test --coverage