-
Notifications
You must be signed in to change notification settings - Fork 6.1k
Description
Type of issue
Outdated article
Description
Section with the issued Link: https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-code-coverage?tabs=windows#code-coverage-tooling
Link Destination: https://github.com/Microsoft/vstest-docs/blob/main/docs/extensions/datacollector.md
Intention for Lookup this Docs page
I am searching for information of using test coverage for unit Testing of .NET 9, .NET 10+ targeting Applications.
Specifically, I found a dotnet-coverage dotnet CLI Tool name used, while reading the GitHub Copilot Agent https://github.com/awesome-copilot/agents/CSharpExpert.agent.md in the Agent instructions Section for Code Coverage and now I was searching for information, in which Cases I would like to use this, since the regular dotnet CLI does already has a build-in dotnet test CLI command 🤔
This knowledge or (advanced?) dotnet tool could potentially be interesting to know about for me, because in my last Project where I asked Copilot for create Unit tests (xUnit, Shouldly Assertions) for an Extension, it seemed to be unable to get the IDE (VS Code / VS 2022) Test Explorer - Test Coverage Report, to fullfill my request to ensure 100% Test Coverage of my future public API's.
The Testing Project did include in this case the coverlet.collector.
What I would like to be informed in this article:
- Get Started with Creating and using Test Coverage toolset (I was assuming that this issued Link would lead me to this?)
- What Options do we have to get Test Coverage
Problem
- The Link "Your first DataCollector" redirects to a Repository, that was Archived in 2022.
- this Ressource should be considered as outdated & unmaintained information state => Not recommendable to be used, especially not in production scenarios!
Commonly Archived Repositories are potentially to be considered not longer to be up to date- .NET SDK, C# Depreciation, Testing Framework Version
- eventual used NuGet Package Version Updates, Breaking Changes that may result in required Changes in Getting Started Guide
- the destination of the issued Link is currently only a md file, not included/embeeded directly in the ms docs
Expectation
- Update Link to a current and maintained destination
- Include guide (which is either way a markdown file) as regular docs page (html) instead of Sample-src-like path, if you don't mean to actually link to sample code only, because web page docs normally provide:
- better formatting / Rendering of the information -> Consumer & Learning Expirience
- Search Engine finding of this informations & Guide
Additional Information
In case you may need to re-work this Guide either way, I would like to kindly request a MS Learn path/module(s) for this to be added, or (if existant already) to be linked to this instead 🚀
Page URL
https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-code-coverage?tabs=windows
Content source URL
https://github.com/dotnet/docs/blob/main/docs/core/testing/unit-testing-code-coverage.md
Document Version Independent Id
ab6ce421-f5e5-94f1-e707-32763b3a6a24
Platform Id
c4fee4a9-6f2b-131d-94db-041bd4940d7e
Article author
Metadata
- ID: 588a6d72-f70f-15f8-7505-5db491c8a8c6
- PlatformId: c4fee4a9-6f2b-131d-94db-041bd4940d7e
- Service: dotnet-fundamentals