development/vscode
development/vscode
1
0
Fork 0
mirror of https://github.com/Microsoft/vscode synced 2024-07-17 11:07:22 +00:00
Code Issues Actions 10 Packages Projects Releases Wiki Activity
vscode/test
History
Joao Moreno 050e66fdad fix smoketest in tfs
2018-05-02 16:52:45 +02:00
..
electron smoketest 2018-04-17 10:54:00 +02:00
smoke fix smoketest in tfs 2018-05-02 16:52:45 +02: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 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