Skip to content

Bump MSTest.TestFramework from 3.10.4 to 4.1.0#1067

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/Philips.CodeAnalysis.Test/MSTest.TestFramework-4.1.0
Closed

Bump MSTest.TestFramework from 3.10.4 to 4.1.0#1067
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/Philips.CodeAnalysis.Test/MSTest.TestFramework-4.1.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Mar 12, 2026

Updated MSTest.TestFramework from 3.10.4 to 4.1.0.

Release notes

Sourced from MSTest.TestFramework's releases.

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:

[TestClass]
public sealed class Test1
{
    [TestMethod]
    public void TestMethod1()
    {
        var animal = "Tiger";
        var zoo = new Zoo();
        Assert.That(() => zoo.GetAnimal() == animal);
    }
}

public class Zoo
{
    public string GetAnimal()
    {
        return "Giraffe";
    }
}
Assert.That(() => zoo.GetAnimal() == animal) failed.
Details:
    animal = "Tiger"     
    zoo.GetAnimal() = "Giraffe"

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:

[TestClass]
public sealed class Test1
{
    [TestMethod]
    public void TestMethod1()
    {
        string animal = null;
        Assert.AreEqual("Giraffe", animal);
    }
}
 ... (truncated)

## 4.0.0-preview.25372.6

This is a prerelease of MSTest v4. Docs on migration from v3 to v4 are in progress. We are working towards addressing the items tracked in #​1285 and #​5762

## 4.0.0-preview.25358.7

This is a prerelease of MSTest v4. Docs on migration from v3 to v4 are in progress. We are working towards addressing the items tracked in https://github.com/microsoft/testfx/issues/1285 and https://github.com/microsoft/testfx/issues/5762

## 3.11.1

See the release notes [here](https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#​3.11.1)

## 3.11.0

See the release notes [here](https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#​3.11.0)

## 3.10.5

See the release notes [here](https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#​3.10.5)


Commits viewable in [compare view](https://github.com/microsoft/testfx/compare/v3.10.4...v4.1.0).
</details>

@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Mar 12, 2026
---
updated-dependencies:
- dependency-name: MSTest.TestFramework
  dependency-version: 4.1.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/nuget/Philips.CodeAnalysis.Test/MSTest.TestFramework-4.1.0 branch from d9ad7b8 to d0ad1fe Compare April 6, 2026 01:08
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Apr 10, 2026

Looks like MSTest.TestFramework is updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Apr 10, 2026
@dependabot dependabot Bot deleted the dependabot/nuget/Philips.CodeAnalysis.Test/MSTest.TestFramework-4.1.0 branch April 10, 2026 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants