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
add logging to the Fine Code Coverage tool window (#227)
* add logging to the Fine Code Coverage tool window
* Fine Code Coverage link to FCC Output Window Pane
* Ensure output window is open before activating FCC pane.
* refactor responsibilities
* Use font and colors / environment font both for font-family and font-size in combination with dpi.
* delete test that does not apply anymore
Download this extension from the [Visual Studio Market Place](https://marketplace.visualstudio.com/items?itemName=FortuneNgwenya.FineCodeCoverage)
5
+
Download this extension from the [Visual Studio Market Place ( vs 2019 )](https://marketplace.visualstudio.com/items?itemName=FortuneNgwenya.FineCodeCoverage), [Visual Studio Market Place ( vs 2022 )](https://marketplace.visualstudio.com/items?itemName=FortuneNgwenya.FineCodeCoverage2022)
6
6
or download from [releases](https://github.com/FortuneN/FineCodeCoverage/releases). Older versions can be obtained from [here](https://ci.appveyor.com/project/FortuneN/finecodecoverage/history).
7
7
8
-
---------------------------------------
8
+
---
9
9
Prerequisites
10
10
11
11
Only that the test adapters are nuget packages. For instance, the NUnit Test Adapter extension is not sufficient.
12
12
FCC will copy your test dll and dependencies to a sub folder this may affect your tests. The alternative is to set the option AdjacentBuildOutput to true.
13
-
---------------------------------------
13
+
14
+
---
14
15
15
16
Introduction
16
17
17
18
Fine Code Coverage works by reacting to the visual studio test explorer, providing coverage from each test project containing tests that you have selected
18
-
to run. This coverage is presented as a single unified report as well as coloured margins alongside your code.
19
+
to run. This coverage is presented as a single unified report in the Fine Code Coverage Tool Window as well as coloured margins alongside your code.
19
20
This coverage is not dynamic and represents the coverage obtained from the last time you executed tests.
20
21
When the coverage becomes outdated, you can click the 'FCC Clear UI' button in Tools or run coverage again.
21
22
23
+
Details of how FCC is progressing with code coverage can be found in the Coverage Log tab in the Fine Code Coverage Tool Window with more detailed logs in the FCC Output Window Pane. If you experience issues then providing the logs from the output window will help to understand the nature of the problem.
24
+
22
25
The coverage is provided by either [OpenCover](https://github.com/OpenCover/opencover) for old style projects and [Coverlet](https://github.com/coverlet-coverage/coverlet)
23
26
for new style sdk projects. FCC provides an abstraction over both so that it is possible to ignore the differences between the two but there are circumstances where
24
27
it is important to be aware of cover tool that will be run. This is most apparent when Coverlet is used, please read on for the specifics.
@@ -28,7 +31,7 @@ but there may be a preview version that you want to use. This can be configured
28
31
Configuration is available with Visual Studio settings and project msbuild properties. All visual studio settings can be overridden from test project settings and some settings
0 commit comments