ec41f20c40
* playwright - initial version
* browser - use existing page and not create new context
* macOS: document how to remove the security flag
* smoke test - allow to run against server build with --build option
* do not rely on args
* fix path for windows
* smoke test - smoke 💄 and -ci option
|
||
|---|---|---|
| .. | ||
| 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