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
In case of network behind the proxy, the following variables must be set:
4
-
5
-
-`http_proxy` - URL to proxy, incl. protocol and port, e.g. http://acme.com:80
6
-
-`no_proxy` - URL patterns that must not use proxy. In particular, corporate/internal NPM module repositories must be enumerated in no_proxy env var.
7
-
8
-
Internally (in package.json), the globalAgent/bootstrap is used with `GLOBAL_AGENT_{HTTP,NO}_PROXY`
9
-
set to the appropriate env variable. The environment variables `http_proxy` and `no_proxy` are read by npm package manager.
10
-
11
-
12
-
# Prepare for testing
13
-
14
-
Ensure that all necessary npm modules are installed. Run
15
-
-`npm install`
16
-
to update the local node_modules module cache, if any changes were pulled for `package.json`.
17
-
18
-
You need to compile the VisualVM extension itself, and the test code before launching the tests.
19
-
-`npm run compile`
20
-
-`npm run pretest`
21
-
22
-
23
-
# Run the tests from the CLI
24
-
1
+
# Proxy setup
2
+
3
+
In case of network behind the proxy, the following variables must be set:
4
+
5
+
-`http_proxy` - URL to proxy, incl. protocol and port, e.g. http://acme.com:80
6
+
-`no_proxy` - URL patterns that must not use proxy. In particular, corporate/internal NPM module repositories must be enumerated in no_proxy env var.
7
+
8
+
Internally (in package.json), the globalAgent/bootstrap is used with `GLOBAL_AGENT_{HTTP,NO}_PROXY`
9
+
set to the appropriate env variable. The environment variables `http_proxy` and `no_proxy` are read by npm package manager.
10
+
11
+
12
+
# Prepare for testing
13
+
14
+
Ensure that all necessary npm modules are installed. Run
15
+
-`npm install`
16
+
to update the local node_modules module cache, if any changes were pulled for `package.json`.
17
+
18
+
You need to compile the VisualVM extension itself, and the test code before launching the tests.
19
+
-`npm run compile`
20
+
-`npm run pretest`
21
+
22
+
23
+
# Run the tests from the CLI
24
+
25
25
Tests can be executed by `npm run test`. The test bootstrap will download a separate installation of vscode into `.vscode-test` directory and then duplicated into `output/a vscode-test` to test the space in path of vscode installation. The testing environment will use a **separate** extensions dir (`.vscode-test/extensions`) and user dir (`.vscode-test/user-data`). The tested vscode installation is completely separated from the development one.
0 commit comments