vscode/test
2020-02-04 15:02:52 +01:00
..
automation CSS smoketest fix for high DPI on Windows 2020-02-03 12:50:27 +01:00
browser use playwright for unit tests 2020-02-04 15:02:52 +01:00
electron Adopt latest istanbul libraries 2020-01-14 11:09:29 +01:00
smoke remove the timeout 2020-02-03 11:49:10 +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
browser.js
cgmanifest.json
coverage.js Don't instrument any test code for coverage (#86608) 2020-01-14 11:10:51 +01:00
css.mock.js
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