Граф коммитов

10 Коммитов

Автор SHA1 Сообщение Дата
Kevin Cunnane 152fccff2a Support code coverage for our VSCode extension. (#273)
- Included a new launch config that supports running with code coverage.
- Coverage is stored in a coverage folder as both LCOV file and HTML report (in sub folder)
- Added new scripts in our build machine to run with code coverage. Will enable a run that uses code coverage once this is merged
- To view code coverage while developing, install the LCOV VSCode extension, enable it and then hit F1 -> LCOV Menu -> Enable Decorations. This will highlight covered / missed lines in green and red.

Note: The HTMLContent codebase is not currently covered. With recent changes to minify this it breaks the remapping tool we use.

Detailed notes
- Coverage uses a config file to load settings. This is copied at the start of each task
- If tests fail, the process exit code will be 1. We should still write out code coverage in these cases as this is a useful detail even on runs with some test failures.

- On Windows, the extension is loaded (pulling in all source files via require) before the test runner is configured. Since instrumentation happens by hooking the require call, this meant that instrumentation never happened on Windows. To resolve this, we invalidate the Module cache for our source files so they are reloaded the next time anything requires them. At this point they are instrumented as expected. There is a minor risk to this if we had some global state or deeper integration test, but this doesn't impact any existing unit tests and is needed to unblock code coverage

* Skip coverage of HTMLContent due to crash
- With the latest HTMLContent changes to minify & uglify the code, the remap-istanbul component responsible for js -> ts remapping crashes trying to parse the sourceMap entries in the file. This is due to lack of whitespace between code which it expects - basically, it's not set up to run against such compact code
- Disabling coverage of this part of the code until this issue is resolved
2016-11-07 12:56:10 -08:00
Karl Burtram 5c4de34039 Merge dogfood build #2 release branch into dev. 2016-10-24 14:32:10 -07:00
Karl Burtram 44e0879f9a Add embedded Getting Started guide (#120)
* Add prompt to view embedded release notes.

* Add Getting Started guide.

* Correct the display condition
2016-09-28 15:20:49 -07:00
Karl Burtram b8d2ce1851 Add C++ metadata files to .gitignore 2016-09-15 20:04:09 -07:00
Leila Lali d6593bd1eb downloading the SQL tools service if does not exist (#70)
* downloading the SQL tools service if does not exist before loading the extension
2016-09-13 15:57:29 -07:00
Karl Burtram 695b0e741c Bump SqlToolsService nuget package version 2016-09-01 10:27:06 -07:00
Karl Burtram 3d4c5fbeb3 Untabify gulpfile.js file 2016-08-16 22:38:46 -07:00
Karl Burtram c043faeabf Pull SqlToolsService host binaries from Nuget instead of as checked in
binaries.
2016-08-16 10:15:33 -07:00
Anthony Dresser e0ef372da4 Slick gridwith angular2 (#7)
* Refactored the project to run the front end code as a separate npm package

* Added Slickgrid as UI component rather than Backgrid

* Added Gulp scripts for building
2016-08-01 18:18:36 -07:00
Karl Burtram 2e96b1f24b Initial commit to GitHub. 2016-06-26 11:49:47 -07:00