ckaczor/azuredatastudio
1
0
Fork 0
mirror of https://github.com/ckaczor/azuredatastudio.git synced 2026-02-17 02:51:36 -05:00
Code Issues Packages Projects Releases Wiki Activity

Add troubleshooting to test docs (#17991)

Browse Source
This commit is contained in:
Charles Gagnon
2022-01-05 14:30:41 -08:00
committed by GitHub
parent e11b1ed2a3
commit 075d9a8268
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
test/README.md
View File

@@ -68,3 +68,9 @@ The same principle can be applied to the vscode/azdata APIs. The object in this
To generate a report combining the code coverage for extensions + core run `node ./test/combineCoverage`. Currently this will combine coverage from the Core Unit Tests, Extension Unit Tests and Extension Integration tests - see above docs for instructions on how to run those to generate coverage. To generate a report combining the code coverage for extensions + core run `node ./test/combineCoverage`. Currently this will combine coverage from the Core Unit Tests, Extension Unit Tests and Extension Integration tests - see above docs for instructions on how to run those to generate coverage.
Once ran the combined coverage report will be located in `./test/coverage`. Once ran the combined coverage report will be located in `./test/coverage`.
## Troubleshooting
### When debugging extension unit tests my breakpoints aren't being hit
There's a known issue when code coverage is enabled that breakpoints won't be hit. See https://github.com/microsoft/azuredatastudio/issues/17985 for more details and a workaround.