Files
azuredatastudio/test
Anthony Dresser 87765e8673 Vscode merge (#4582)
* Merge from vscode 37cb23d3dd4f9433d56d4ba5ea3203580719a0bd

* fix issues with merges

* bump node version in azpipe

* replace license headers

* remove duplicate launch task

* fix build errors

* fix build errors

* fix tslint issues

* working through package and linux build issues

* more work

* wip

* fix packaged builds

* working through linux build errors

* wip

* wip

* wip

* fix mac and linux file limits

* iterate linux pipeline

* disable editor typing

* revert series to parallel

* remove optimize vscode from linux

* fix linting issues

* revert testing change

* add work round for new node

* readd packaging for extensions

* fix issue with angular not resolving decorator dependencies
2019-03-19 17:44:35 -07:00
..
2019-03-15 13:09:45 -07:00
2019-03-19 17:44:35 -07:00
2019-03-15 13:09:45 -07:00
2019-03-15 13:09:45 -07:00
2019-03-15 13:09:45 -07:00
2019-02-21 17:56:04 -08:00
2019-02-21 17:56:04 -08:00
2018-09-04 14:55:00 -07:00

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 azuredatastudio 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