Bump the small-change group with 3 updates

[dependabot]

Bumps the small-change group with 3 updates: MSTest.TestAdapter, MSTest.TestFramework and Microsoft.Data.SqlClient.

Updates MSTest.TestAdapter from 3.3.1 to 3.4.3

Release notes

Sourced from MSTest.TestAdapter's releases.

v3.4.3

See the release notes here

v.3.4.2

See the release notes here

v3.4.1

See the release notes here

v3.4.0

Here are the highlights of the current release, full change log is available below:

microsoft/testfx@v3.3.1...v3.4.0

MSTest

New and improved analyzers

We've added more code analyzers to help you prevent mistakes, and to ensure a consistent code style of your tests.

One example of a new analyzer that was added in 3.4.0 is MSTEST0024: Do not store TestContext in static members. This analyzer has info severity by default, and will show a message, when you store TestContext in a static member in your class. This is not recommended, and you should be using a TestContext property instead:

The other analyzers added in this release:

• MSTEST0017: Assertion arguments should be passed in the correct order by @​Evangelink in #2256
• MSTEST0019: Prefer TestInitialize over ctor by @​Evangelink in #2580
• MSTEST0020: Prefer ctors over TestInitialize methods by @​Evangelink in #2582
• MSTEST0021: Prefer Dispose over TestCleanup methods by @​Evangelink in #2585
• MSTEST0022: Prefer 'TestCleanup' methods over Dispose by @​Evangelink in #2586
• MSTEST0023: Do not negate boolean assertions by @​Evangelink in #2594
• MSTEST0024: Do not store TestContext in static members by @​Evangelink in #2597
• Add PreferAssertFailOverAlwaysFalseConditionsAnalyzer by @​Youssef1313 in #2799

If you've just learned about MSTest analyzers, please also check out the analyzers that were added in previous releases. They will help you ensure that your test classes and test methods are recognized by MSTest and are not accidentally ignored.

The analyzers are automatically installed with the MSTest NuGet meta-package. But can also be installed separately using the MSTest.Analyzers NuGet package.

More timeout options

Timeout can now be specified on all fixture methods, including ClassCleanup, AssemblyCleanup, TestCleanup and TestInitalize. In this case I want my [ClassCleanup] to time out after 1 second:

Alternatively timeouts can be specified through runsettings. For example like this:

<RunSettings>
  <MSTest>
</tr></table> 

... (truncated)

Changelog

Sourced from MSTest.TestAdapter's changelog.

[3.4.3] - 2024-05-30

See full log here

Fixed

• Revert version of Code Coverage to 17.10.4 by @​Evangelink in #3048

Artifacts

• MSTest: 3.4.3
• MSTest.TestFramework: 3.4.3
• MSTest.TestAdapter: 3.4.3
• MSTest.Analyzers: 3.4.3
• MSTest.Sdk: 3.4.3
• Microsoft.Testing.Extensions.CrashDump: 1.2.1
• Microsoft.Testing.Extensions.HangDump: 1.2.1
• Microsoft.Testing.Extensions.HotReload: 1.2.1
• Microsoft.Testing.Extensions.Retry: 1.2.1
• Microsoft.Testing.Extensions.TrxReport: 1.2.1

[3.4.2] - 2024-05-30

See full log here

Fixed

• Use latest released version for Playwright and Aspire by @​Evangelink in #3024
• Fix project samples for 3.4 by @​Evangelink in #3032
• Fix assembly resolution with DeploymentItem by @​Evangelink in #3034

Artifacts

• MSTest: 3.4.2
• MSTest.TestFramework: 3.4.2
• MSTest.TestAdapter: 3.4.2
• MSTest.Analyzers: 3.4.2
• MSTest.Sdk: 3.4.2
• Microsoft.Testing.Extensions.CrashDump: 1.2.1
• Microsoft.Testing.Extensions.HangDump: 1.2.1
• Microsoft.Testing.Extensions.HotReload: 1.2.1
• Microsoft.Testing.Extensions.Retry: 1.2.1
• Microsoft.Testing.Extensions.TrxReport: 1.2.1

[3.4.1] - 2024-05-27

See full log here

Fixed

... (truncated)

Commits

• 27aa72e Revert version of Code Coverage to 17.10.4 (#3048)
• 1225aed Update Versions.props
• a502340 Fix assembly resolution with DeploymentItem (#3034)
• 5d5c982 Fix project samples for release 3.4 (#3032)
• c08d299 Use latest released version for Playwright and Aspire (#3024)
• 394f7a4 [rel/3.4] Update dependencies from devdiv/DevDiv/vs-code-coverage (#3013)
• efc614f Fix assembly resolution error (#2948)
• b4ab8ee Bump version to 3.4.1
• bafa77b Use VSTest 17.10 (#2902)
• 7fd9f76 Use latest version of TA and MSTest.Engine (#2885)
• Additional commits viewable in compare view

Updates MSTest.TestFramework from 3.3.1 to 3.4.3

Release notes

Sourced from MSTest.TestFramework's releases.

v3.4.3

See the release notes here

v.3.4.2

See the release notes here

v3.4.1

See the release notes here

v3.4.0

Here are the highlights of the current release, full change log is available below:

microsoft/testfx@v3.3.1...v3.4.0

MSTest

New and improved analyzers

We've added more code analyzers to help you prevent mistakes, and to ensure a consistent code style of your tests.

One example of a new analyzer that was added in 3.4.0 is MSTEST0024: Do not store TestContext in static members. This analyzer has info severity by default, and will show a message, when you store TestContext in a static member in your class. This is not recommended, and you should be using a TestContext property instead:

The other analyzers added in this release:

• MSTEST0017: Assertion arguments should be passed in the correct order by @​Evangelink in #2256
• MSTEST0019: Prefer TestInitialize over ctor by @​Evangelink in #2580
• MSTEST0020: Prefer ctors over TestInitialize methods by @​Evangelink in #2582
• MSTEST0021: Prefer Dispose over TestCleanup methods by @​Evangelink in #2585
• MSTEST0022: Prefer 'TestCleanup' methods over Dispose by @​Evangelink in #2586
• MSTEST0023: Do not negate boolean assertions by @​Evangelink in #2594
• MSTEST0024: Do not store TestContext in static members by @​Evangelink in #2597
• Add PreferAssertFailOverAlwaysFalseConditionsAnalyzer by @​Youssef1313 in #2799

If you've just learned about MSTest analyzers, please also check out the analyzers that were added in previous releases. They will help you ensure that your test classes and test methods are recognized by MSTest and are not accidentally ignored.

The analyzers are automatically installed with the MSTest NuGet meta-package. But can also be installed separately using the MSTest.Analyzers NuGet package.

More timeout options

Timeout can now be specified on all fixture methods, including ClassCleanup, AssemblyCleanup, TestCleanup and TestInitalize. In this case I want my [ClassCleanup] to time out after 1 second:

Alternatively timeouts can be specified through runsettings. For example like this:

<RunSettings>
  <MSTest>
</tr></table> 

... (truncated)

Changelog

Sourced from MSTest.TestFramework's changelog.

[3.4.3] - 2024-05-30

See full log here

Fixed

• Revert version of Code Coverage to 17.10.4 by @​Evangelink in #3048

Artifacts

• MSTest: 3.4.3
• MSTest.TestFramework: 3.4.3
• MSTest.TestAdapter: 3.4.3
• MSTest.Analyzers: 3.4.3
• MSTest.Sdk: 3.4.3
• Microsoft.Testing.Extensions.CrashDump: 1.2.1
• Microsoft.Testing.Extensions.HangDump: 1.2.1
• Microsoft.Testing.Extensions.HotReload: 1.2.1
• Microsoft.Testing.Extensions.Retry: 1.2.1
• Microsoft.Testing.Extensions.TrxReport: 1.2.1

[3.4.2] - 2024-05-30

See full log here

Fixed

• Use latest released version for Playwright and Aspire by @​Evangelink in #3024
• Fix project samples for 3.4 by @​Evangelink in #3032
• Fix assembly resolution with DeploymentItem by @​Evangelink in #3034

Artifacts

• MSTest: 3.4.2
• MSTest.TestFramework: 3.4.2
• MSTest.TestAdapter: 3.4.2
• MSTest.Analyzers: 3.4.2
• MSTest.Sdk: 3.4.2
• Microsoft.Testing.Extensions.CrashDump: 1.2.1
• Microsoft.Testing.Extensions.HangDump: 1.2.1
• Microsoft.Testing.Extensions.HotReload: 1.2.1
• Microsoft.Testing.Extensions.Retry: 1.2.1
• Microsoft.Testing.Extensions.TrxReport: 1.2.1

[3.4.1] - 2024-05-27

See full log here

Fixed

... (truncated)

Commits

• 27aa72e Revert version of Code Coverage to 17.10.4 (#3048)
• 1225aed Update Versions.props
• a502340 Fix assembly resolution with DeploymentItem (#3034)
• 5d5c982 Fix project samples for release 3.4 (#3032)
• c08d299 Use latest released version for Playwright and Aspire (#3024)
• 394f7a4 [rel/3.4] Update dependencies from devdiv/DevDiv/vs-code-coverage (#3013)
• efc614f Fix assembly resolution error (#2948)
• b4ab8ee Bump version to 3.4.1
• bafa77b Use VSTest 17.10 (#2902)
• 7fd9f76 Use latest version of TA and MSTest.Engine (#2885)
• Additional commits viewable in compare view

Updates Microsoft.Data.SqlClient from 5.2.0 to 5.2.1

Release notes

Sourced from Microsoft.Data.SqlClient's releases.

Stable release v5.2.1

[Stable release 5.2.1] - 2024-05-31

Changed

• Upgraded Azure.Identity version from 1.10.3 to 1.11.3 #2492, #2528
• Upgraded Microsoft.Identity.Client version from 4.56.0 to 4.60.3 #2492
• Code Health improvements: #2467

Fixed

• Fixed connection errors on Linux when Data Source property contains both named instance and port #2436
• Fixed SqlConnection.FireInfoMessageEventOnUserErrors when set to true throws an exception #2505
• Fixed exception when using DATETIMEOFFSET(n) in a TVP if n is 1, 2, 3, or 4 #2506
• Reverted PR #1983 which caused connection failure delays when using OpenAsync #2507
• Fixed SqlConnection.Clone() to include AccessTokenCallback #2527

Changelog

Sourced from Microsoft.Data.SqlClient's changelog.

[Stable release 5.2.1] - 2024-05-31

This update brings the below changes over the previous release:

Changed

• Upgraded Azure.Identity version from 1.10.3 to 1.11.3 #2492, #2528
• Upgraded Microsoft.Identity.Client version from 4.56.0 to 4.60.3 #2492
• Code Health improvements: #2467

Fixed

• Fixed connection errors on Linux when Data Source property contains both named instance and port #2436
• Fixed SqlConnection.FireInfoMessageEventOnUserErrors when set to true throws an exception #2505
• Fixed exception when using DATETIMEOFFSET(n) in a TVP if n is 1, 2, 3, or 4 #2506
• Reverted PR #1983 which caused connection failure delays when using OpenAsync #2507
• Fixed SqlConnection.Clone() to include AccessTokenCallback #2527

Commits

• 7af2438 Fix | Enhance certificate validation (#2487)
• 808d4c3 Change | Separate tests for NetFx and NetCore - NetFx-Only Connection String ...
• 815e5ab Doc | Fix SNI dependencies of 5.1 and 5.2 release notes (#2537)
• b7c4007 Enhancement | Add trace logs for packet size (#2522)
• b178ba5 Fix | Clone of SqlConnection should include AccessTokenCallback (#2525)
• cd7a3d1 Updating Azure.Identity version to 1.11.3 (#2526)
• 5cb73fd Merged SqlClientFactory between .NET Core and Framework (#2369)
• cc6ea21 Streamline conditional compilation symbols (#2486)
• 9a71c94 Update build guide for Linux (#2499)
• 4c0f013 Remove UWP (uap) references and special cased code (#2483)
• Additional 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