development/vscode
development/vscode
1
0
Fork 0
mirror of https://github.com/Microsoft/vscode synced 2024-11-05 18:29:38 +00:00
Code Issues Projects Releases Packages Wiki Activity
vscode/test
History
Benjamin Pasero 959246744b status - simplify by not needing element ID
2019-05-28 18:20:56 +02:00
..
electron remove winjs-promise - fixes #53526 2018-12-13 10:28:26 +01:00
smoke status - simplify by not needing element ID 2019-05-28 18:20:56 +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
index.html
mocha.opts
README.md

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