ckaczor/sqltoolsservice
1
0
Fork 0
mirror of https://github.com/ckaczor/sqltoolsservice.git synced 2026-01-13 17:23:02 -05:00
Code Issues Packages Projects Releases Wiki Activity

Remove code coverage from STS (#1537)

Browse Source 
* WIP removal of code coverage

* more coverage removed

* more fixes

* fix tests
This commit is contained in:
Alex Ma
2022-06-10 13:53:43 -07:00
committed by GitHub
parent b182e9fe53
commit 5e3d24bbfa
23 changed files with 13 additions and 4579 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/guide/building_sqltoolsservice.md
View File

@@ -22,8 +22,7 @@
## Run Tests
The SQL Tools Service has several different types of tests such as unit tests, "connected" tests,
integration tests, perf tests and stress tests. Additionally, there is also test configuration
scripts to collect code coverage results.
integration tests, perf tests and stress tests.
### Running Unit Tests
@@ -41,15 +40,4 @@ xUnit.net .NET CLI test runner (64-bit win10-x64)
=== TEST EXECUTION SUMMARY ===
Microsoft.SqlTools.ServiceLayer.Test Total: 434, Errors: 0, Failed: 0, Skipped: 0, Time: 21.139s
SUMMARY: Total: 1 targets, Passed: 1, Failed: 0.
```
### Collecting Code Coverage
> Code coverage requires a SQL Server instance installed on the localhost with Integrated Authentication
> configured for the current user executing the test suite.
> Code coverage can only be collected from Windows at this time.
1. Run `npm install` from test/CodeCoverage directory.
2. Run `runintegration.cmd` from test/CodeCoverage directory.
3. Code coverage results will be available in the test/CodeCoverage/reports/index.html report.
```