Conversation
Bumps Microsoft.NET.Test.Sdk from 17.14.1 to 18.0.1 Bumps MSTest from 3.10.0 to 4.1.0 --- updated-dependencies: - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.0.1 dependency-type: direct:production update-type: version-update:semver-major - dependency-name: MSTest dependency-version: 4.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Test Results201 tests ±0 194 ✅ - 2 55s ⏱️ +28s For more details on these failures, see this check. Results for commit c55f972. ± Comparison against base commit 21586b5. |
|
@dependabot rebase |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
|
Looks like this PR is closed. If the branch still exists, you can re-open the PR and then use |
Updated Microsoft.NET.Test.Sdk from 17.14.1 to 18.0.1.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.0.1
What's Changed
Fixing an issue with loading covrun64.dll on systems that have .NET 10 SDK installed: https://learn.microsoft.com/en-us/dotnet/core/compatibility/sdk/10.0/code-coverage-dynamic-native-instrumentation
Internal changes
Full Changelog: microsoft/vstest@v18.0.0...v18.0.1
18.0.0
What's Changed
Internal fixes and updates
... (truncated)
Commits viewable in compare view.
Updated MSTest from 3.10.0 to 4.1.0.
Release notes
Sourced from MSTest's releases.
4.0.2
See the release notes here
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: