Skip to content

chore(nuget)!: Update nuget MSTest ( 3.11.1 ➔ 4.2.1 )#6

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-mstest-monorepo
Open

chore(nuget)!: Update nuget MSTest ( 3.11.1 ➔ 4.2.1 )#6
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-mstest-monorepo

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate bot commented Apr 10, 2026

This PR contains the following updates:

Package Change Age Confidence
MSTest 3.11.14.2.1 age confidence

Release Notes

microsoft/testfx (MSTest)

v4.2.1

See the release notes here

v4.1.0

See the release notes here

v4.0.2

See the release notes here

v4.0.1

See the release notes here

v4.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);
    }
}
Error Message: Assert.AreEqual failed. Expected:<Giraffe>. Actual:<>. 
'expected' expression: '"Giraffe"', 'actual' expression: 'animal'.
Breaking changes

We hidden many types that should have never been public in the first place. We believe that most of the changes won't have any real user impact. For the changes where we expect user impact migration guide from v3 is provided: https://learn.microsoft.com/dotnet/core/testing/unit-testing-mstest-migration-v3-v4

See the MSTest changelog here: https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#4.0.0
See the Microsoft.Testing.Platform changelog here: https://github.com/microsoft/testfx/blob/main/docs/Changelog-Platform.md#2.0.0

Full changelog here: microsoft/testfx@v3.11.0...v4.0.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Every minute (* * * * *)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-mstest-monorepo branch 4 times, most recently from fe3eaf7 to 10c8552 Compare April 10, 2026 12:33
@renovate renovate bot changed the title chore(nuget)!: Update nuget MSTest ( 3.9.1 ➔ 4.2.1 ) chore(nuget)!: Update nuget MSTest ( 3.11.1 ➔ 4.2.1 ) Apr 10, 2026
@renovate renovate bot force-pushed the renovate/major-mstest-monorepo branch from 10c8552 to 9a32bbc Compare April 10, 2026 12:35
@renovate renovate bot changed the title chore(nuget)!: Update nuget MSTest ( 3.11.1 ➔ 4.2.1 ) chore(nuget)!: Update nuget MSTest ( 3.9.1 ➔ 4.2.1 ) Apr 10, 2026
@renovate renovate bot force-pushed the renovate/major-mstest-monorepo branch 2 times, most recently from 4536fc4 to 47959d2 Compare April 10, 2026 12:41
@renovate renovate bot changed the title chore(nuget)!: Update nuget MSTest ( 3.9.1 ➔ 4.2.1 ) chore(nuget)!: Update nuget MSTest ( 3.11.1 ➔ 4.2.1 ) Apr 10, 2026
@mynameisbogdan mynameisbogdan force-pushed the main branch 4 times, most recently from b61373d to a337540 Compare April 10, 2026 16:00
@renovate renovate bot force-pushed the renovate/major-mstest-monorepo branch from 47959d2 to d6d9afc Compare April 10, 2026 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants