development/vscode
development/vscode
1
0
Fork 0
mirror of https://github.com/Microsoft/vscode synced 2024-09-13 21:55:38 +00:00
Code Issues Packages Projects Releases Wiki Activity
vscode/test
History
Sandeep Somavarapu 9f4c0dcb67 Fix #38847
2017-11-22 12:54:21 +01:00
..
electron Fix #38847 2017-11-22 12:54:21 +01:00
smoke Fix two non-readonly statics in smoke tests 2017-11-20 15:48:43 -08:00
all.js Fixes #23183: Cannot use mocha --run anymore 2017-03-24 22:27:14 +01:00
assert.js Hello Code 2015-11-13 14:39:38 +01:00
browser.js Restore mocha --browser 2017-06-26 15:16:34 +02:00
index.html Restore mocha --browser 2017-06-26 15:16:34 +02:00
mocha.opts clean up test scripts, bring back html server tests 2017-11-15 11:15:57 +01:00
OSSREADME.json Hello Code 2015-11-13 14:39:38 +01:00
README.md update test/README 2017-05-22 16:09:58 +02: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 gulp. 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