development/vscode
development/vscode
1
0
Fork 0
mirror of https://github.com/Microsoft/vscode synced 2024-10-31 07:52:49 +00:00
Code Issues Projects Releases Packages Wiki Activity
vscode/test
History
isidor fe747f81c0 debug smoke: match ona a substring for a specific stack frame due to a potential sufix "readonly node content" 
fixes #56069
2018-08-15 12:14:20 +02:00
..
electron fix unit tests on windows 2018-08-07 06:43:25 -07:00
smoke debug smoke: match ona a substring for a specific stack frame due to a potential sufix "readonly node content" 2018-08-15 12:14:20 +02:00
tree tree: fix expand/collapse 2018-08-10 23:15:45 +02:00
all.js Fixes #54899: Do not attempt to use real css loader in mocha unit tests 2018-08-08 17:52:05 +02:00
assert.js
browser.js Restore mocha --browser 2017-06-26 15:16:34 +02: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 clean up test scripts, bring back html server tests 2017-11-15 11:15:57 +01:00
OSSREADME.json
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