development/vscode
development/vscode
1
0
Fork 0
mirror of https://github.com/Microsoft/vscode synced 2024-07-17 02:57:19 +00:00
Code Issues Actions 9 Packages Projects Releases Wiki Activity
vscode/test
History
Dirk Baeumer 0938fe05a7 Use dot reporter under Windows since spec doesn't handle ANSI color characters due to the fact that tests are executed as an electron app
2017-05-24 09:59:53 +02:00
..
electron Use dot reporter under Windows since spec doesn't handle ANSI color characters due to the fact that tests are executed as an electron app 2017-05-24 09:59:53 +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 fix up lint errors, cleanup build folder 2016-03-07 12:56:32 +01:00
index.html Leading whitespace fixes 2015-11-19 12:56:08 +01:00
mocha.opts [html] add tests to test.sh 2017-02-17 19:41:32 +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