vscode/test
SteVen Batten 61c52d0dda
GridLayout perf improvements (#79614)
* add deserialization to splitview

* add new grid deserialization test to index.html

* working mostly

* branchnode should invert orthogonality in splitview

* fix issue with sidebar snapping

* cleanup and make splitview api more explicit

* hook up children sash reset

* adopt single deserialize (PR feedback)
2019-08-26 08:12:00 -07:00
..
electron builds - prevent window.open() in tests 2019-08-21 15:20:49 +02:00
smoke Teardown server on SIGTERM 2019-08-20 10:17:54 -07:00
splitview GridLayout perf improvements (#79614) 2019-08-26 08:12:00 -07:00
tree demo 2019-07-23 13:55:11 +02:00
all.js Adopt latest istanbul for coverage information 2019-07-16 11:52:51 +02:00
assert.js
browser.js
cgmanifest.json
coverage.js Adopt latest istanbul for coverage information 2019-07-16 11:52:51 +02:00
css.mock.js
index.html
mocha.opts
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