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
Johannes Rieken 21b671d921 browser-test: exit(1) when test failed
2020-02-06 16:39:45 +01:00
..
automation Web - run smoke tests using playwright (#89918) 2020-02-04 17:23:27 +01:00
browser browser-test: exit(1) when test failed 2020-02-06 16:39:45 +01:00
electron Adopt latest istanbul libraries 2020-01-14 11:09:29 +01:00
smoke Web - run smoke tests using playwright (#89918) 2020-02-04 17:23:27 +01:00
splitview splitview: use TLayoutContext 2019-11-27 15:27:24 +01:00
tree fix manual tree tests 2019-09-09 15:09:47 +02:00
all.js Adopt latest istanbul for coverage information 2019-07-16 11:52:51 +02:00
assert.js update assert.js-copy 2020-02-05 12:10:02 +01:00
browser.js
cgmanifest.json rename isOnlyDevelopmentDependency to developmentDependency 2018-11-21 16:17:52 +01:00
coverage.js Don't instrument any test code for coverage (#86608) 2020-01-14 11:10:51 +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
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