development/vscode
development/vscode
1
0
Fork 0
mirror of https://github.com/Microsoft/vscode synced 2024-09-13 13:46:13 +00:00
Code Issues Packages Projects Releases Wiki Activity
vscode/test
History
Benjamin Pasero 4f074abe22 Smoke test for multi root (#31059) 
* wip

* fix for windows

* add some tests

* only run multi root test on windows

* fix bug with opening files into a workspace that opens (enables smoke test)

* document how to run against out of source

* enable test for all OS
2017-07-20 16:01:21 +02:00
..
electron eng - print test failure to renderer console for easy reveal in dev tools 2017-06-06 12:59:52 +02:00
smoke Smoke test for multi root (#31059) 2017-07-20 16:01:21 +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 [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