Bump MSTest.TestAdapter from 3.3.1 to 3.5.0 in /Source

[dependabot[bot]]

Bumps MSTest.TestAdapter from 3.3.1 to 3.5.0.

Release notes

Sourced from MSTest.TestAdapter's releases.

v3.5.0

See the release notes here

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:

https://github.com/microsoft/testfx/compare/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:

... (truncated)

Changelog

Sourced from MSTest.TestAdapter's changelog.

[3.5.0] - 2024-07-15

See full log here

Added

• Add overloads to CollectionAssert.AreEquivalent/AreNotEquivalent with IEqualityComparer<T> by @​engyebrahim in #3130
• Add code fix for MSTEST0017 by @​engyebrahim in #3091
• Add SDK samples from rel/3.4 by @​nohwnd in #3074
• Add suppressors for VSTHRD200 by @​Evangelink in #2926
• Add code fix for TestInitializeShouldBeValidAnalyzer by @​Evangelink in #2890
• Add code fix for ClassCleanupShouldBeValidAnalyzer by @​Evangelink in #2883
• Add code fix for AssemblyInitializeShouldBeValidAnalyzer by @​Evangelink in #2882
• Add code fix for ClassInitializeShouldBeValidAnalyzer by @​Evangelink in #2884
• Add code fixes for AssemblyCleanupShouldBeValidAnalyzer by @​Evangelink in #2866
• Add sample of MSTest runner for WinUI by @​Evangelink in #2834
• MSTEST0032: Always pass assertions by @​engyebrahim in #3238
• MSTEST0025: add support for Assert.IsNull by @​engyebrahim in #3233
• Update fixture analyzers to report on missing [TestClass] by @​Evangelink in #3252
• Customize MSTest runner banner by @​Evangelink in #3235
• Analyzer: Ensure to use Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute and not System.ComponentModel.DescriptionAttribute by @​engyebrahim in #3202
• MSTEST0030: Type containing [TestMethod] must be a [TestClass] by @​engyebrahim in #3199
• leverage DoesNotReturnIfAttribute for better assertion by @​SimonCropp in #3168
• Assertions: add support for [StringSyntax(CompositeFormat)] by @​Evangelink in #3185
• Display fixture (Assembly/Class Initialize/Cleanup) methods as "test" entries by @​fhnaseer in #2904
• Improve display name for string and char by @​MichelZ in #3082
• Improve display name when DataRow contains arrays by @​MichelZ in #3053
• TestCaseFilter with custom properties by @​engyebrahim in #3015
• MSTEST0029: Public methods should be test methods by @​engyebrahim in #3065
• Avoid conditionals inside assertions analyzer by @​fhnaseer in #2848
• Localize console service by @​nohwnd in #2900
• Code fix for TestCleanupShouldBeValidAnalyzer by @​Evangelink in #2887
• Run and fail tests when ITestDataSource.GetData returns empty IEnumerable by @​fhnaseer in #2865
• Include timeout duration in timeout message by @​engyebrahim in #2877
• Flow execution context across fixture methods when using timeout by @​Evangelink in #2843
• MSTest runner: allow overriding TestRunParameters by @​Evangelink in #3106

Housekeeping

• Fix some IDEXXX warnings by @​Evangelink in #2844
• fix install-windows-sdk path by @​SimonCropp in #2930
• Fix release years in changelog by @​Evangelink in #3001
• Fix some diagnostics happening only in VS by @​Evangelink in #3016
• Add acceptance tests for info with all extensions by @​Evangelink in #3119
• Refactor STA pool code by @​MarcoRossignoli in #3231
• Make IProcess disposable by @​Evangekunj in #3120
• Use GetTypes() instead of DefinedTypes by @​SimonCropp in #3112
• Use ConcurrentDictionary for attribute cache, and avoid func by @​nohwnd in #3062
• Lower reflection overhead by @​nohwnd in #2839
• avoid array alloc in CommandLineParseResult by using IReadOnlyList by @​SimonCropp in #3027

... (truncated)

Commits

• 5b79b58 Ensure stable versions before moving to MSTest
• 359466b Bump platform to 1.3.1
• d348a10 Use expansion in a variable
• 8bff296 NEw test at fixing pipeline
• 2684869 Fix official pipeline for releasing products
• 0dd4f1c [rel/3.5] Fix ResultFiles placement in TRX report (#3264)
• 5a7bb00 Fix changelog and update changelog generator
• 076e5e9 Revert "Update deps"
• 52fed4b Update deps
• 3bf1d6c Bump dependencies (#3257)
• 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 ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.