Skip to content

Sync dotnet test (VSTest) docs with microsoft/vstest repo#2

Closed
azat-msft wants to merge 1 commit into
mainfrom
fix-dotnet-test-vstest-crossref
Closed

Sync dotnet test (VSTest) docs with microsoft/vstest repo#2
azat-msft wants to merge 1 commit into
mainfrom
fix-dotnet-test-vstest-crossref

Conversation

@azat-msft

@azat-msft azat-msft commented Jul 14, 2026

Copy link
Copy Markdown
Owner

Thorough cross-reference of docs/core/tools/dotnet-test-vstest.md (the VSTest content of dotnet-test.md) against the microsoft/vstest /docs directory (main @ f48a80f2c). Went option-by-option and fixed outdated/incomplete information.

Content source breakdown

Change vstest source Type
--filter property table + mapping note filter.md Adapted
--diag tracelevel sub-option + allowed values diagnose.md Adapted
TestRunParameters command-line support + RunSettings precedence RunSettingsArguments.md Adapted
RunSettingsArguments link fix repo move Microsoft/vstest-docs -> microsoft/vstest Fixed

Details

  • Filter property table corrected to match the authoritative filter.md:
    • xUnit: Category -> Traits (xUnit filters on trait keys; Category is just a common trait name).
    • NUnit: added TestCategory and Property (previously only Name, Category, Priority).
    • Added a clarifying note on how xUnit traits and NUnit properties/categories map to filter expressions.
  • --diag tracelevel documented: you can append ;tracelevel=<LEVEL> (off, error, warning, info, verbose; default verbose).
  • TestRunParameters from the command line documented (available since the .NET 5 SDK), plus the note that RunSettings arguments take precedence over a .runsettings file.
  • Fixed the RunSettingsArguments link from the archived Microsoft/vstest-docs repo to the current microsoft/vstest repo.
  • Bumped ms.date.

Other topics (Arguments, blame/crash-dump options, --collect, --logger, -s|--settings, Examples) were compared against configure.md, report.md, analyze.md, and environment-variables.md and found accurate/consistent — no changes needed.

Note

This PR was created with the assistance of AI (ai-usage: ai-assisted, already present in the article).

@azat-msft
azat-msft force-pushed the fix-dotnet-test-vstest-crossref branch from b1e9669 to 34ee2ea Compare July 14, 2026 20:05
Cross-referenced docs/core/tools/dotnet-test-vstest.md against the microsoft/vstest /docs directory and fixed outdated/incomplete content:

- Corrected the --filter property table (filter.md): xUnit uses Traits (not Category); NUnit adds TestCategory and Property; added a note on how traits/properties/categories map to filters.

- Documented the --diag tracelevel sub-option and its allowed values (diagnose.md).

- Documented TestRunParameters command-line support (since .NET 5 SDK) and RunSettings precedence (RunSettingsArguments.md).

- Updated the RunSettingsArguments link from the archived Microsoft/vstest-docs repo to microsoft/vstest.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 5857e78c-41dd-4f82-a41b-cbf1fe5f35cb
@azat-msft
azat-msft force-pushed the fix-dotnet-test-vstest-crossref branch from 34ee2ea to 0e0bee7 Compare July 14, 2026 20:20
Comment thread docs/core/tools/dotnet-test-vstest.md
azat-msft added a commit that referenced this pull request Jul 15, 2026
Fold complementary changes from #2 into this PR: --diag tracelevel sub-option, TestRunParameters command-line support with RunSettings precedence, corrected filter property table (xUnit Traits, NUnit TestCategory/Category/Property) with a trait/property mapping note, and the RunSettingsArguments repo link fix.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: c46887ab-e194-4295-9afd-01a25c405c76
@azat-msft

Copy link
Copy Markdown
Owner Author

Closing in favor of #1, which now folds in these VSTest cross-reference fixes (--diag tracelevel, TestRunParameters command-line support with RunSettings precedence, corrected filter property table with trait/property mapping note, and the RunSettingsArguments link fix) alongside the existing enrichment changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants