Bump Microsoft.NET.Test.Sdk and MSTest #23
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated Microsoft.NET.Test.Sdk from 17.12.0 to 18.0.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.0.0
What's Changed
Internal fixes and updates
... (truncated)
17.14.1
What's Changed
Full Changelog: microsoft/vstest@v17.14.0...v17.14.1
17.14.0
What's Changed
.NET versions updated
This version of VS Test upgraded .NET to net8 and net9. All projects targeting net6.0 (or other end-of-life .NET target frameworks) should pin their version of Microsoft.NET.Test.SDK to 17.13.0, or update the projects to net8 or newer. We remain backwards compatible with previous versions of Microsoft.NET.Test.SDK. This change does NOT prevent you from:
It also has no impact on .NET Framework projects, where we continue targeting .NET Framework 4.6.2.
Changes
Internal version updates and fixes
New Contributors
... (truncated)
17.14.0-preview-25107-01
What's Changed
.NET versions updated
This version of VS Test upgraded .NET to net8 and net9. All projects targeting net6.0 (or other end-of-life .NET target frameworks) should pin their version of Microsoft.NET.Test.SDK to 17.13.0, or update the projects to net8 or newer. We remain backwards compatible with previous versions of Microsoft.NET.Test.SDK. This change does NOT prevent you from:
It also has no impact on .NET Framework projects, where we continue targeting .NET Framework 4.6.2.
Changes
Internal version updates and fixes
Will probably revert before release:
New Contributors
Full Changelog: microsoft/vstest@v17.13.0...v17.14.0-preview-25107-01
17.13.0
What's Changed
Add letter number among valid identifiers in class name by @nohwnd in Add letter number among valid identifiers in class name microsoft/vstest#13868
Fix formatting in Runner by @mthalman in Fix formatting in Runner microsoft/vstest#13871
Downgrade xunit skip warning to info by @nohwnd in Downgrade xunit skip warning to info microsoft/vstest#10381
Add msdia for arm64 into nuget by @nohwnd in Add msdia for arm64 into nuget microsoft/vstest#10382
Enable native debugging for vstest.console by @ocitrev in Enable native debugging for vstest.console microsoft/vstest#10401
Fix RFCs links by @Youssef1313 in Fix RFCs links microsoft/vstest#10424
Convert to auto property by @nohwnd in Convert to auto property microsoft/vstest#10365
Update Versions.props by @nohwnd in Update Versions.props microsoft/vstest#10378
Enable TSA by @jakubch1 in Enable TSA microsoft/vstest#10385
Arm64 dia by @nohwnd in Arm64 dia microsoft/vstest#10390
Update source-build team references by @MichaelSimons in Update source-build team references microsoft/vstest#10388
Exclude .signature.p7s from nupkg file count by @ellahathaway in Exclude .signature.p7s from nupkg file count microsoft/vstest#10418
Set NetCurrent so that it doesn't roll forward automatically by @ViktorHofer in Set NetCurrent so that it doesn't roll forward automatically microsoft/vstest#10622
New Contributors
Full Changelog: microsoft/vstest@v17.12.0...v17.13.0
Commits viewable in compare view.
Updated MSTest from 3.6.4 to 4.0.1.
Release notes
Sourced from MSTest's releases.
4.0.1
See the release notes here
4.0.0
What is new?
Assert.That
MSTest v4 adds a new type of assertion, that allows you to write any expression, and it will inspect the result to give you more information on failure. Providing a very flexible way to assert complicated expressions. Here a simple example:
CallerArgumentExpression
CallerArgumentExpression is consumed by all assertions, to make them aware of the expressions used in the assertion. In the example below, we now know what both the expected and actual values are. But also what value they come from, giving us opportunity to provide better error messages: