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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+12-10
Original file line number
Diff line number
Diff line change
@@ -42,8 +42,11 @@ Then clone the repository and install NPM packages:
42
42
43
43
### Run
44
44
45
-
Due to the monorepo structure of the project, you must have the `aws-toolkit-vscode/packages/toolkit` folder open as root folder in the workspace.
46
-
The easiest way to open the project: File > Open Workspace from File > choose `aws-toolkit-vscode/aws-toolkit-vscode.code-workspace`
45
+
Due to the monorepo structure of the project, you must open the project using the
46
+
`aws-toolkit-vscode.code-workspace` project file.
47
+
48
+
1. Run the `File: Open Workspace from File...` command in vscode.
49
+
2. Select the `aws-toolkit-vscode.code-workspace` project file.
47
50
48
51
To run the extension from VSCode as a Node.js app:
49
52
@@ -164,8 +167,7 @@ See [web.md](./docs/web.md) for working with the web mode implementation of the
164
167
See [TESTPLAN.md](./docs/TESTPLAN.md) to understand the project's test
165
168
structure, mechanics and philosophy.
166
169
167
-
You can run tests directly from VSCode. Due to the monorepo structure of the project, you must have the `aws-toolkit-vscode/packages/toolkit` folder open as root folder in the workspace.
168
-
The easiest way to open the project: File > Open Workspace from File > choose `aws-toolkit-vscode/aws-toolkit-vscode.code-workspace`
170
+
You can run tests directly from VSCode. Due to the monorepo structure of the project, you must [open the project via the `aws-toolkit-vscode.code-workspace` project file](#run).
169
171
170
172
1. Select `View > Debug`, or select the Debug pane from the sidebar.
171
173
2. From the dropdown at the top of the Debug pane, select the `Extension Tests` configuration.
@@ -180,12 +182,13 @@ Tests will write logs to `./.test-reports/testLog.log`.
180
182
181
183
#### Run a specific test
182
184
183
-
To run a single test in VSCode, do any one of:
185
+
To run a single test in VSCode, do any _one_ of the following:
184
186
185
187
- Run the _Extension Tests (current file)_ launch-config.
186
-
- Use Mocha's [it.only()](https://mochajs.org/#exclusive-tests) or `describe.only()`.
187
-
- Run in your terminal:
188
-
188
+
- Note: if you don't see this in the vscode debug menu, confirm that you opened the project
189
+
[via the `aws-toolkit-vscode.code-workspace` project file](#run).
190
+
- or... Use Mocha's [it.only()](https://mochajs.org/#exclusive-tests) or `describe.only()`.
191
+
- or... Run in your terminal:
189
192
- Unix/macOS/POSIX shell:
190
193
```
191
194
TEST_FILE=../core/src/test/foo.test.ts npm run test
@@ -194,8 +197,7 @@ To run a single test in VSCode, do any one of:
194
197
```
195
198
$Env:TEST_FILE = "../core/src/test/foo.test.ts"; npm run test
196
199
```
197
-
198
-
- To run all tests in a particular subdirectory, you can edit
200
+
- or... To run all tests in a particular subdirectory, you can edit
199
201
`src/test/index.ts:rootTestsPath` to point to a subdirectory:
0 commit comments