-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move some docs from VS docs to dotnet/docs #4938
Comments
@Evangelink Was this considered before? |
Yes that's something I wanted to do and when I just saw your PR I realized this is something I didn't do. |
Let's add @ghogen to this conversation. |
Let me also reformulate my thinking: we should keep the pages on VS side related to how you create a test, run a test etc but anything common or generic to CLI should be moved over to the dotnet MSTest doc and referred to by the VS one as we are mainly updating this one. |
The VS Test content is owned by @Mikejo5000 Mike Jones. |
If the unit testing content is VS-centered, we would normally want to keep it in the VS docs. We also need to avoid moving any articles that are also applicable to C++, such as the code coverage articles. From a quick review, it looks to me like the main candidates for getting moved to .NET are: MSTest / Data-driven tests: Use the Assert classes Unit tests for generic methods @Evangelink It looks like the VS articles on VSTest.Console.exe command-line and also the article on using the runsettings from the command line are also supported for C++ code coverage, so it seems they should stay in the VS docs. |
Some docs are present in VS, e.g:
https://learn.microsoft.com/en-us/visualstudio/test/how-to-create-a-data-driven-unit-test?view=vs-2022
while others are present in .NET docs, e.g:
https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-mstest-writing-tests-attributes
We should move any docs that are not VS-specific from VS docs and add proper redirections.
FYI @gewarren @IEvangelist @BillWagner
The text was updated successfully, but these errors were encountered: