mirror of https://github.com/ckaczor/azuredatastudio.git synced 2026-01-14 01:25:37 -05:00

Files

Anthony Dresser 9fe4237033 Maintain Query State (#2571 )

* add results view stating

* working through the bugs

* handle various resizing bugs

* gnale resizing better

* fix tests by adding missing node module

* formatting

* refactor interfaces out to get around testing restrictions

* more refactoring of importants to avoid loading errors

2018-09-13 18:42:29 -07:00

electron

Merge VS Code 1.26.1 (#2394 )

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

smoke

Merge VS Code 1.26.1 (#2394 )

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

tree

Merge VS Code 1.26.1 (#2394 )

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

all.js

Maintain Query State (#2571 )

2018-09-13 18:42:29 -07:00

assert.js

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

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

browser.js

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

2017-11-09 14:30:27 -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

OSSREADME.json

Merge VS Code 1.26.1 (#2394 )

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

README.md

Merge VS Code 1.23.1 (#1520 )

2018-06-05 11:24:51 -07: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 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