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
* fix: code coverage not reporting for amazon q
Problem:
- Codecoverage for amazon q wasn't actually generating any lcov.info information since the c8rc.json lived in core and amazonq couldn't find it
Solution:
- Make a c8rc file inside of q for configuring c8
- note: tried hoisting the c8rc from core into the root and sharing it between the two projects but it seems to break file paths
- Add code coverage report for q
- Change code coverage directory for toolkit
- Update codecov codewhisperer/featureDev paths
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-6Lines changed: 1 addition & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -218,12 +218,7 @@ To run tests against a specific folder in VSCode, do any one of:
218
218
219
219
### Coverage report
220
220
221
-
You can find the coverage report at `./coverage/index.html` after running the tests. Tests ran from the workspace launch config won't generate a coverage report automatically because it can break file watching. A few manual steps are needed instead:
222
-
223
-
- Run the command `Tasks: Run Build Task` if not already active
224
-
- Instrument built code with `npm run instrument`
225
-
- Exercise the code (`Extension Tests`, `Integration Tests`, etc.)
226
-
- Generate a report with `npm run report`
221
+
You can find the coverage report at `./coverage/amazonq/lcov-report/index.html` and `./coverage/core/lcov-report/index.html` after running the tests. Tests ran from the workspace launch config won't generate a coverage report automatically because it can break file watching.
Copy file name to clipboardExpand all lines: docs/arch_develop.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,8 +37,7 @@ Current quirks of the current monorepo status that should be resolved/evaluated
37
37
- This package contains shortcuts to some of the `npm` scripts found in the subproject(s).
38
38
-`createRelease` and `newChange` run at the subproject level only, e.g. from root level, try npm run createRelease -w packages/toolkit
39
39
- To run a script not present in the root `package.json`, use `npm run -w packages/toolkit <script>`
40
-
-`coverage/`, `.test-reports/`, `node_modules/` are hoisted to the project root. As more subprojects are added,
41
-
we will need to evaluate how to merge and publish coverage reports.
40
+
-`coverage/`, `.test-reports/`, `node_modules/` are hoisted to the project root.
42
41
-`dist/` however remains at the subproject level, along with a local `node_modules/`. See [`npm workspaces`](https://docs.npmjs.com/cli/v8/using-npm/workspaces)
43
42
for more info on how `node_modules/` hoisting works.
44
43
- Because of `node_modules/` hoisting, references to this folder in code access the root project modules folder. This may be
0 commit comments