Bump the dotnet group with 6 updates #5465

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.0.2).
</details>

Updated [MSTest.TestFramework](https://github.com/microsoft/testfx) from 3.10.4 to 4.0.2.

<details>
<summary>Release notes</summary>

_Sourced from [MSTest.TestFramework's releases](https://github.com/microsoft/testfx/releases)._

## 4.0.2

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

## 4.0.1

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

## 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:

```csharp
[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.0.2).
</details>

Updated [NUnit.Analyzers](https://github.com/nunit/nunit.analyzers) from 4.10.0 to 4.11.2.

<details>
<summary>Release notes</summary>

_Sourced from [NUnit.Analyzers's releases](https://github.com/nunit/nunit.analyzers/releases)._

## 4.11.2

NUnit Analyzers 4.11.2 - November 2, 2025

This release of the NUnit Analyzers fixes a problem in the `NUnit2057` analyzer for unnecessary use of lambda 
expressions. The release also extends `NUnit2021` so that it can determining if `Is.NaN` or `Is.Not.NaN` constraints
are used on incompatible types.

The release contains contributions from the following users (in alphabetical order):
* @MaceWindu
* @manfred-brands
* @stevenaw

Issues Resolved

Features and Enhancements
* #929 Alert when using Is.NaN or Is.Not.NaN on an incompatible type

Bugs
* #945 [NUnit2057] Reported for Throws assert

## 4.11.1

NUnit Analyzers 4.11.1 - October 30, 2025

This release of the NUnit Analyzers fixes a regression related to the analysis of nullable enum parameters in
`NUnit1001` and `NUnit1031`. The release also contains a new analyzer and codefix for unnecessary usage of lambda
expressions in asserts.

The release contains contributions from the following users (in alphabetical order):
* @MaceWindu
* @maksim-sovkov
* @manfred-brands

Issues Resolved

Features and Enhancements
* #927 Add new rule for unnecessary use of lambda expressions

Bugs
* #939 NUnit1001 - false positive for arguments with nullable enum parameters
* #938 [NUnit1031] False positive for nullable structs

## 4.11.0

NUnit Analyzers 4.11 - October 28, 2025

This release of the NUnit Analyzers includes improvements and fixes related to `IDisposable` handling and initialization 
in `SetUp` and `OneTimeSetUp` methods. It also introduces the ability to configure additional methods that should be 
treated as `SetUp` and `TearDown` methods by the analyzers. This can be done in the `.editorconfig`, and there are four 
configurations for this:

* `dotnet_diagnostic.NUnit.additional_setup_methods`
* `dotnet_diagnostic.NUnit.additional_teardown_methods`
* `dotnet_diagnostic.NUnit.additional_one_time_setup_methods`
* `dotnet_diagnostic.NUnit.additional_one_time_teardown_methods`

Each configuration accepts a list of method names, separated by commas, semicolons, or spaces. For example:

```ini
dotnet_diagnostic.NUnit.additional_setup_methods = CustomSetup, MyInit

As in recent releases, a major part of this work was contributed by @manfred-brands.

The release contains contributions from the following users (in alphabetical order):

@AlisonAMorrison
@BodrickLight
@cbersch
@manfred-brands
@mikkelbu
@PiotrKlecha
@sbe-schleupen

Issues Resolved

Features and Enhancements

#921 NUnit1032 - disposals in overridden methods not detected
#919 NUnit1032/NUnit3002 - local functions not analyzed
#918 NUnit2045 - false positive for inline usings
#911 NUnit3002 doesn't recognize the using statement.
#910 using declarations not recognized by NUnit2045

Bugs

#922 NUnit1001 - false positive for arguments with generic parameters
#914 Wrong position of NUnit1001 diagnostic for TestCase with four parameters or more

Tooling, Process, and Documentation

#926 chore: Bump NUnit3TestAdapter
#908 chore: bump version
#885 Bump to NUnit version 4.4 when this is released

Commits viewable in compare view.

Updated NUnit3TestAdapter from 5.1.0 to 5.2.0.

Release notes

Sourced from NUnit3TestAdapter's releases.

5.2.0

See release notes

Commits viewable in compare view.

Updated xunit.runner.visualstudio from 3.1.4 to 3.1.5.

Release notes

Sourced from xunit.runner.visualstudio's releases.

No release notes found for this version range.

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

Bumps Microsoft.NET.Test.Sdk from 17.14.1 to 18.0.1 Bumps MSTest.TestAdapter from 3.10.4 to 4.0.2 Bumps MSTest.TestFramework from 3.10.4 to 4.0.2 Bumps NUnit.Analyzers from 4.10.0 to 4.11.2 Bumps NUnit3TestAdapter from 5.1.0 to 5.2.0 Bumps xunit.runner.visualstudio from 3.1.4 to 3.1.5 --- updated-dependencies: - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet - dependency-name: MSTest.TestAdapter dependency-version: 4.0.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet - dependency-name: MSTest.TestFramework dependency-version: 4.0.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: dotnet - dependency-name: NUnit.Analyzers dependency-version: 4.11.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: NUnit3TestAdapter dependency-version: 5.2.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dotnet - dependency-name: xunit.runner.visualstudio dependency-version: 3.1.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dotnet ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot bot added .NET Pull requests that update .net code dependencies Pull requests that update a dependency file labels Nov 26, 2025

This was referenced Nov 26, 2025

Bump the dotnet group with 3 updates #5462

Closed

Bump the dotnet group with 2 updates #5463

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Bump the dotnet group with 6 updates #5465

Bump the dotnet group with 6 updates #5465

Uh oh!

dependabot bot commented on behalf of github Nov 26, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Bump the dotnet group with 6 updates #5465

Are you sure you want to change the base?

Bump the dotnet group with 6 updates #5465

Uh oh!

Conversation

dependabot bot commented on behalf of github Nov 26, 2025

18.0.1

What's Changed

Internal changes

18.0.0

What's Changed

Internal fixes and updates

4.0.2

4.0.1

4.0.0

What is new?

Assert.That

CallerArgumentExpression

CallerArgumentExpression

5.2.0

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant