vscode/test
2019-12-09 09:37:52 -08:00
..
automation fixes #78384 2019-12-05 14:21:50 +01:00
electron fixes #84455 2019-11-13 10:40:09 +01:00
smoke fixes #78384 2019-12-05 14:21:50 +01:00
splitview splitview: use TLayoutContext 2019-11-27 15:27:24 +01:00
tree fix manual tree tests 2019-09-09 15:09:47 +02:00
all.js Adopt latest istanbul for coverage information 2019-07-16 11:52:51 +02:00
assert.js replace void 0 with undefined 2019-01-03 11:20:19 -08:00
browser.js
cgmanifest.json rename isOnlyDevelopmentDependency to developmentDependency 2018-11-21 16:17:52 +01:00
coverage.js Don't instrument any test code for coverage 2019-12-09 09:37:52 -08:00
css.mock.js Fixes #54899: Do not attempt to use real css loader in mocha unit tests 2018-08-08 17:52:05 +02:00
index.html
mocha.opts
README.md

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