This extension is built around Coverlet to provide fast & easy code coverage in to Visual Studio
New in v1.16.6
You can change the watch folder and filter in the options menu now. You must restart Visual Studio after changing watch folder
v1.16.5
Partial support for VS2019 (no more exception) Can only use watch folder for now.
v1.16.4
Supports VS 2019 (but was broken for long time sorry)
v1.16.2
Settings menu in "Tools > Options > PrestoCoverage"
Can set colours using hexadecimal including transparency, for example: #FF006BF7
v1.16.2 - Option to clear coverage on change, like build.
v1.15
Bug fixes (1.15.1 Fixed breakpoint not hit on Test Debug - and will start to use "patch version" from now on for bug fixes)
v1.14
Automatic coverage discovery after test execution. (uses Coverlet.Core.dll - does not require dotnet tool or NuGet package)
Can still use c:\coverlet but if directory does not exist this will not be used. Automatic coverage always on. will not conflict only merge.
Added More bugs, not sure where. (please let me know. do not rage uninstall)
v1.12
Brings merging of line visits from several coverage files. e.g; Unit Test and Integration Test results can have various line coverage. If you put both files in the extension will show all the coverage. update or delete the coverage files automatically updates VS
Road map
Full Visual Studio support... as time permits, then these ...
v.1.16.x - Insights to help me capture exceptions in the wild (and consent in Options)
v.1.17 - Enhanced branching information. (Flat branches show as covered but cannot tell which parts where covered)
v.1.18 - Create my own VS Pane to show Coverage details. Percentages covered by project, file, class, method...
Tested frameworks
nUnit net4.5 -> Net4.5 Class
nunit net4.6.1 -> Standard 2.0 Class
xUnit core 2.1 -> Core 2.1 Class
more test coming
Known problems
Moq - Seems to be a problem with Moq (investigating)
Signed code - If you sign code during debug, Coverlet changes the DLL and Security Verification will prevent the runners from starting. No work around!
This is my first VS Extension. I try my best to make the plugin stable because I use it myself and don't want to get annoyed by it. But my knowledge is very limited and VSIX development documentation is extremely difficult to understand. Please do not rage uninstall, just drop me a message on GitHub - Will sort it.
