Uh oh!
There was an error while loading. Please reload this page.
Bump MSTest from 3.9.2 to 4.3.0 - #20051
Conversation
--- updated-dependencies: - dependency-name: MSTest dependency-version: 4.3.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Test this change out locally with the following install scripts (Action run 33541613133) VSCode
Azure CLI
|
Brendan Burns (brendandburns)
commented
Jul 13, 2026
Copilot please fix CI/CD |
Fixed. The CI failures were caused by MSTest 4.x bundling Changes made:
|
A newer version of MSTest exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
Brendan Burns (brendandburns)
commented
Sep 1, 2026
Copilot please update MSTest to the latest version and make sure CI/CD passes |
Brendan Burns (brendandburns)
commented
Sep 1, 2026
Copilot please update MSTest to the latest version and make sure CI/CD passes |
…rability Co-authored-by: brendandburns <5751682+brendandburns@users.noreply.github.com>
Updated MSTest to 4.3.3 (the current latest) in commit |
Brendan Burns (brendandburns)
commented
Sep 1, 2026
Copilot please do the migrations marked as TODO in this change and remove the suppressions from this change. |
…icDataSourceType, fix assertion issues Co-authored-by: brendandburns <5751682+brendandburns@users.noreply.github.com>
…0' into dependabot/nuget/src/MSTest-4.3.0 # Conflicts: # src/Bicep.Core.UnitTests/ApiVersion/ApiVersionProviderTests.cs # src/Bicep.Core.UnitTests/Configuration/RootConfigurationTests.cs # src/Bicep.Core.UnitTests/Modules/OciArtifactModuleReferenceTests.cs # src/Bicep.Core.UnitTests/Modules/TemplateSpecModuleReferenceTests.cs # src/Bicep.Core.UnitTests/Registry/ArtifactDispatcherTests.cs # src/Bicep.LangServer.IntegrationTests/TelemetryTests.cs # src/Bicep.LangServer.UnitTests/Completions/ModuleReferenceCompletionProviderTests.cs Co-authored-by: brendandburns <5751682+brendandburns@users.noreply.github.com>
Done. All the TODO migrations have been completed and the suppressions removed from
All test projects build with 0 errors and tests pass. |
Brendan Burns (brendandburns)
commented
Sep 1, 2026
Copilot please fix CI/CD |
…bility in ResultAssertionsExtensionsTests Co-authored-by: brendandburns <5751682+brendandburns@users.noreply.github.com>
…lean from removing bicep AppHost in RpcClient.Tests Co-authored-by: brendandburns <5751682+brendandburns@users.noreply.github.com>
Fixed two remaining CI failures:
|
Copilot The Build workflow failed for this dependabot dependency-update PR (run ID: 33532934228). Please investigate and fix the failing tests so this PR can be merged. Failed run: https://github.com/Azure/bicep/actions/runs/33532934228 Things to consider for this repo:
Please keep changes minimal and focused on compatibility with the new dependency versions. |
Brendan Burns (brendandburns)
commented
Sep 2, 2026
Copilot The Build workflow failed for this dependabot dependency-update PR (run ID: 33532934228). Please investigate and fix the failing tests so this PR can be merged. Failed run: https://github.com/Azure/bicep/actions/runs/33532934228 Things to consider for this repo: Baseline tests – if snapshot/baseline files are out of date, regenerate them with |
Brendan Burns (brendandburns)
commented
Sep 3, 2026
Copilot please investigate and fix CI/CD. |
Updated MSTest from 3.9.2 to 4.3.0.
Release notes
Sourced from MSTest's releases.
4.3.0
See the release notes here
4.2.3
See the release notes here
4.2.2
See the release notes here
4.2.1
See the release notes here
4.1.0
See the release notes here
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: