Document MSBuild integration

[nohwnd]

Summary

Document MSTest runner and dotnet test integration and the various options tied to the MSBuild task.

Fixes #Issue_Number (if available)

---

Internal previews

📄 File	🔗 Preview link
docs/core/testing/unit-testing-mstest-runner-integrations.md	Use MSTest runner with dotnet test

[Evangelink]

You will need to also update the toc file to have the correct grouping for this new file.

@IEvangelist would it be possible to introduce folders so we can avoid the need for toc update? I also have some complex toc for the analyzers in another PR.

[IEvangelist]

You will need to also update the toc file to have the correct grouping for this new file.

@IEvangelist would it be possible to introduce folders so we can avoid the need for toc update? I also have some complex toc for the analyzers in another PR.

Folders don't have any impact on the TOC. While you can structure your files however you deem necessary, they're not related to the TOC. The TOC is managed via the toc.yml.

[adegeo]

@Evangelink @IEvangelist folders do impact SEO and I believe we're already at the limit before we get dinged.

[Evangelink]

Folders don't have any impact on the TOC. While you can structure your files however you deem necessary, they're not related to the TOC. The TOC is managed via the toc.yml.

That's interesting. I have added a lot of docs for CAxxxx rules and I have never touched the toc.yml and yet the grouping is working as expected.

folders do impact SEO and I believe we're already at the limit before we get dinged.

Is there a way to have something similar to https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1822 for us in testing without having the folders? https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1822? I mean I would like to have something like https://learn.microsoft.com/dotnet/core/testing/mstest/analyzers/MSTEST0001 and https://learn.microsoft.com/dotnet/core/testing/mstest/runner/intro instead of https://learn.microsoft.com/dotnet/core/testing/unit-testing-mstest-runner-intro

[adegeo]

Folders don't have any impact on the TOC. While you can structure your files however you deem necessary, they're not related to the TOC. The TOC is managed via the toc.yml.

That's interesting. I have added a lot of docs for CAxxxx rules and I have never touched the toc.yml and yet the grouping is working as expected.

Someone probably did it for you and you just didn't notice ;) we do that a lot with the TOC.

folders do impact SEO and I believe we're already at the limit before we get dinged.

Is there a way to have something similar to https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1822 for us in testing without having the folders? https://learn.microsoft.com/en-us/dotnet/fundamentals/code-analysis/quality-rules/ca1822? I mean I would like to have something like https://learn.microsoft.com/dotnet/core/testing/mstest/analyzers/MSTEST0001 and https://learn.microsoft.com/dotnet/core/testing/mstest/runner/intro instead of https://learn.microsoft.com/dotnet/core/testing/unit-testing-mstest-runner-intro

things like CA1822 are error/warning codes and are really reference articles with a very specific search term (CA1822). That term is probably not used in other articles very much and we don't have to worry about other articles interfering with its SEO capabilities. And we sort of expect users to F1 in visual studio and get a direct link to them. Conceptual articles like this one that teach someone how to enable something, we expect them to find by searching for things like "How do I enable MSTest?" so SEO is important here. Google deprioritizes articles with lots of folder segments because they look like spam sites: http://..../new/items/for/sale/list.html

[Evangelink]

things like CA1822 are error/warning codes and are really reference articles with a very specific search term (CA1822). That term is probably not used in other articles very much and we don't have to worry about other articles interfering with its SEO capabilities. And we sort of expect users to F1 in visual studio and get a direct link to them. Conceptual articles like this one that teach someone how to enable something, we expect them to find by searching for things like "How do I enable MSTest?" so SEO is important here. Google deprioritizes articles with lots of folder segments because they look like spam sites: http://..../new/items/for/sale/list.html

I am actually asking for #38845 where I am adding analyzers for MSTest. I do expect the same logic where users will F1 on VS and will look up for the analyzer code. This is also similar to the SYSLIBxxxx issues https://learn.microsoft.com/en-us/dotnet/fundamentals/syslib-diagnostics/syslib0014

[adegeo]

Yeah, that's fine and makes sense for more analyzer content.

[nohwnd]

@adegeo I addressed all the feedbacks now. Can you please accept and merge? :)

[Evangelink]

Ping @adegeo @IEvangelist

[IEvangelist]

A few more nits, otherwise let's

[Evangelink]

A few more nits, otherwise let's

Awesome, thanks! I have applied the changes.

[adegeo]

LGTM!