How should Coverlet be configured if I want to display coverage in VSCode?

[bennage]

My goal is to update coverage info and have it accessible whenever tests are ran in Visual Studio Code. (This is independent of code coverage in our CI/CD process.)

I'm using the .NET Test Explorer and Koverage extensions, in a devcontainer with .NET 8.
.NET Test Explorer is configured such that tests are executed like:
dotnet test --collect:"XPlat Code Coverage;Format=lcov" --no-build --logger "trx;LogFileName=/tmp/some_log.trx"

Every time the tests are ran, I get a new instance of coverage.info inside a folder named with a guid:
./TestResults/<guid>/coverage.info.

Based on what I've read, this seems to be the expected behavior however the Koverage extension is confused when there are multiple copies of coverage.info.

Can I configure Coverlet to overwrite coverage.info such that there's only a single copy?
Or is there a better approach than what I'm doing?

[Bertk]

Please use --results-directory option (see dotnet test command)

--results-directory <RESULTS_DIR>
The directory where the test results are going to be placed. If the specified directory doesn't exist, it's created. The default is TestResults in the directory that contains the project file.

e.g.
--results-directory:"$(Build.SourcesDirectory)\artifacts\reports”

[bennage]

Thank you!

[bennage]

I just tested this, and it's not actually what I'm looking for.
The option allows me produce coverage files at ./artifacts/reports/<guid>/coverage.info instead of ./TestResults/<guid>/coverage.info. I was hoping to overwrite previously created coverage files.

Perhaps I am approaching the problem in the wrong way.
Is there any guidance on how to have coverage updated in vscode after tests are executed?

[Bertk]

coverlet.msbuild.taks allows to set the coverage file path.

coverlet/Documentation/MSBuildIntegration.md

Lines 53 to 59 in 37f6b8c

	The Coverlet MSBuild task sets the `CoverletReport` MSBuild item so that you can easily use the produced coverage reports. For example, using [ReportGenerator](https://github.com/danielpalme/ReportGenerator#usage--command-line-parameters) to generate an html coverage report.
	```xml
	<Target Name="GenerateHtmlCoverageReport" AfterTargets="GenerateCoverageResultAfterTest">
	<ReportGenerator ReportFiles="@(CoverletReport)" TargetDirectory="../html-coverage-report" />
	</Target>
	```

coverlet/Documentation/MSBuildIntegration.md

Lines 41 to 45 in 37f6b8c

	The output of the coverage result can be specified using the `CoverletOutput` property.
	```bash
	dotnet test /p:CollectCoverage=true /p:CoverletOutput='./result.json'
	```

coverage.collect does not support specifying the coverage file path.

coverlet/Documentation/VSTestIntegration.md

Lines 65 to 67 in 37f6b8c

	You can change the output directory using the standard `dotnet test` switch `--results-directory`
	>*NB: By design VSTest platform will create your file under a random named folder(guid string) so if you need stable path to load file to some gui report system(i.e. coveralls, codecov, reportgenerator etc..) that doesn't support glob patterns or hierarchical search, you'll need to manually move resulting file to a predictable folder*

related issue: #1276