mbenningfield1
mbenningfield1
Problem solved by removing the spacing around the "+" and "-" operators. I guess they were being interpreted as list signifiers.
Well that's kinda my point. The coverage is not correct, because that isn't a branch. So you're saying I should raise the issue with Microsoft?
OK, so I gather that it is still an open issue in Coverlet, and that nobody has raised the issue with Microsoft. I'm away from that machine at the moment,...
Definitely using ms code coverage, and both of the cobertura.xml files show the same error for what looks like every fixed statement in the code base.
OK, I have opened an issue with testfx at [issue](https://github.com/microsoft/codecoverage/issues/177), so I'm closing this one.
The FineCodeCoverage window doesn't have to be open to get a coverage report. What happens is that I run the tests, open the window, and it looks like does when...
I think I got them all; there should be a way to export these to a text file.
No, it does it sometimes after I've had the output open several times. As I say, I can't find any rhyme or reason for when it does it. I did...
Microsoft Visual Studio Community 2022 (64-bit) Version 17.14.3 Fine Code coverage Version 1.1.245 As I said, the coverage output is present in the unit test debug directory when it does...
No, the solution is not open source. I'm using mstest by way of the NuGet packages: ``` ``` As I say, when it does it, the output pane shows no...