mirror of https://github.com/ckaczor/azuredatastudio.git synced 2026-02-01 09:35:41 -05:00

Files

Chris LaFreniere d15a3fcc98 Merge from vscode 81d7885dc2e9dc617e1522697a2966bc4025a45d (#5949 )

* Merge from vscode 81d7885dc2e9dc617e1522697a2966bc4025a45d

* Fix vs unit tests and hygiene issue

* Fix strict null check issue

2019-06-10 18:27:09 -07:00

electron

Fix bootstrapping around dashboard (#5040 )

2019-04-15 23:49:40 -07:00

smoke

Merge from vscode 81d7885dc2e9dc617e1522697a2966bc4025a45d (#5949 )

2019-06-10 18:27:09 -07:00

tree

Merge from vscode 591842cc4b71958c81947b254924a215fe3edcbd (#4886 )

2019-04-05 14:14:26 -07:00

all.js

Renable Strict TSLint (#5018 )

2019-04-18 00:34:53 -07:00

assert.js

Merge VS Code 1.31.1 (#4283 )

2019-03-15 13:09:45 -07:00

browser.js

SQL Operations Studio Public Preview 1 (0.23) release source code

2017-11-09 14:30:27 -08:00

cgmanifest.json

Merge from master

2019-02-21 17:56:04 -08:00

css.mock.js

Merge from master

2019-02-21 17:56:04 -08:00

index.html

Merge VS Code 1.26.1 (#2394 )

2018-09-04 14:55:00 -07:00

mocha.opts

Refresh master with initial release/0.24 snapshot (#332 )

2017-12-15 15:38:57 -08:00

README.md

Change vscode folder name to azuredatastudio

2019-03-01 14:32:42 -08: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 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