547cf4e81f
* Run web against actual server Part of #80308 * Fix strict null check errors * Fix folder arg * Disable unit tests and integration tests temporarily * Allow running on node 12 * Fix smoke test condition * Disable continue on error * Add web to server dir * fix smoke test to use build for web * enable in product build Co-authored-by: Benjamin Pasero <benjamin.pasero@gmail.com> |
||
|---|---|---|
| .. | ||
| automation | ||
| electron | ||
| smoke | ||
| splitview | ||
| tree | ||
| all.js | ||
| assert.js | ||
| browser.js | ||
| cgmanifest.json | ||
| coverage.js | ||
| 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