Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Breaking change] For dotnet test, switch -r to alias --runtime instead of --results-dir #21952

Closed
richlander opened this issue Oct 11, 2021 · 0 comments · Fixed by #22497
Closed

[Breaking change] For dotnet test, switch -r to alias --runtime instead of --results-dir #21952

richlander opened this issue Oct 11, 2021 · 0 comments · Fixed by #22497
Labels
Area-DotNet Test untriaged Request triage from a team member

Comments

@richlander
Copy link
Member

richlander commented Oct 11, 2021 •
edited
Loading

Check it out:

rich@mazama:~$ dotnet test --help | grep -- -r
                                            See https://aka.ms/vstest-report
                                          testing. Implies --no-restore.
  -r, --results-directory <RESULTS_DIR>   The directory where the test results
  --runtime <RUNTIME_IDENTIFIER>          The target runtime to test for.
  --no-restore                            Do not restore the project before

-r should be used for --runtime for all verbs.

This is similar to #21389.

https://grep.app/search?q=dotnet%20test%20-r
https://grep.app/search?q=dotnet%20test%20--results-directory
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-DotNet Test untriaged Request triage from a team member labels Oct 11, 2021
This was referenced Oct 11, 2021
Closed
Closed
@richlander richlander changed the title [Breaking change] For dotnet test, switch -r to --runtime instead of --results-dir [Breaking change] For dotnet test, switch -r to alias --runtime instead of --results-dir Oct 11, 2021
@nohwnd nohwnd mentioned this issue Oct 13, 2021
Merged
@MarcoRossignoli MarcoRossignoli mentioned this issue Oct 19, 2021
Merged
@MarcoRossignoli MarcoRossignoli mentioned this issue Nov 6, 2021
Merged
@Evangelink Evangelink mentioned this issue Nov 11, 2022
Merged
mawosoft added a commit to mawosoft/MissingCoverage that referenced this issue Feb 11, 2023
@mawosoft
Release v0.9.2
3febce7 
- Finalize targeting net6.0 with RollForward=Major (use MSBuild property instead of rollForwardOnNoCandidateFx)
- Use dotnet SDK >= 7.0.2
- Fix test.ps1 for breaking change in SDK 7.0 (see dotnet/sdk#21952)
@mawosoft mawosoft mentioned this issue Feb 11, 2023
Merged
mawosoft added a commit to mawosoft/MissingCoverage that referenced this issue Feb 11, 2023
@mawosoft
Release v0.9.2
190b66c 
- Finalize targeting net6.0 with RollForward=Major (use MSBuild property instead of rollForwardOnNoCandidateFx)
- Use dotnet SDK >= 7.0.2
- Fix test.ps1 for breaking change in SDK 7.0 (see dotnet/sdk#21952)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-DotNet Test untriaged Request triage from a team member
Projects
None yet
Milestone
No milestone
1 participant
@richlander