You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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](https://github.com/Microsoft/vscode/wiki/How-to-Contribute#incremental-build) for more details. From the `vscode` folder run:
6
-
7
-
**OS X and Linux**
8
-
9
-
./scripts/test.sh
10
-
11
-
**Windows**
12
-
13
-
scripts\test
14
-
15
-
16
-
## Debug
17
-
18
-
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:
The best way to run the unit tests is from the terminal. To make development changes to unit tests you need to be running `yarn watch`. See [Development Workflow](https://github.com/Microsoft/vscode/wiki/How-to-Contribute#incremental-build) for more details. From the `vscode` folder run:
6
+
7
+
**OS X and Linux**
8
+
9
+
./scripts/test.sh
10
+
11
+
**Windows**
12
+
13
+
scripts\test
14
+
15
+
16
+
## Run (inside browser)
17
+
18
+
You can run tests inside a browser instance too:
19
+
20
+
**OS X and Linux**
21
+
22
+
node test/unit/browser/index.js
23
+
24
+
**Windows**
25
+
26
+
node test\unit\browser\index.js
27
+
28
+
29
+
## Debug
30
+
31
+
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:
0 commit comments