History

Joao Moreno be403842b2 tests		2019-07-01 09:48:59 +02:00
..
electron	tests	2019-07-01 09:48:59 +02:00
smoke	smoke - fix waitForStatusbarText	2019-06-28 15:35:36 +02:00
tree	test dependenices are devDependencies	2019-04-05 17:39:48 +02:00
all.js	remove winjs-promise - fixes #53526	2018-12-13 10:28:26 +01: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
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	Remove unnecessary commented out code	2018-05-28 03:31:02 +03:00
mocha.opts
README.md	Use yarn rather than gulp for building tests	2018-03-12 15:06:19 -04:00

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