microsoft / component-detection

Scans your project to determine what components you use
MIT License
396 stars 81 forks source link

chore(deps): update mstest monorepo to v3.4.0 #1119

Closed renovate[bot] closed 1 month ago

renovate[bot] commented 1 month ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
MSTest.TestAdapter 3.2.2 -> 3.4.0 age adoption passing confidence
MSTest.TestFramework 3.2.2 -> 3.4.0 age adoption passing confidence

Release Notes

microsoft/testfx (MSTest.TestAdapter) ### [`v3.4.0`](https://togithub.com/microsoft/testfx/releases/tag/v3.4.0) Here are the highlights of the current release, full change log is available below: ##### 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: ![image](https://togithub.com/microsoft/testfx/assets/5735905/ab0f95c3-f83e-47b9-a995-87161cb6a61c) The other analyzers added in this release: - MSTEST0017: Assertion arguments should be passed in the correct order by [@​Evangelink](https://togithub.com/Evangelink) in [#​2256](https://togithub.com/microsoft/testfx/pull/2256) - MSTEST0019: Prefer TestInitialize over ctor by [@​Evangelink](https://togithub.com/Evangelink) in [#​2580](https://togithub.com/microsoft/testfx/pull/2580) - MSTEST0020: Prefer ctors over TestInitialize methods by [@​Evangelink](https://togithub.com/Evangelink) in [#​2582](https://togithub.com/microsoft/testfx/pull/2582) - MSTEST0021: Prefer Dispose over TestCleanup methods by [@​Evangelink](https://togithub.com/Evangelink) in [#​2585](https://togithub.com/microsoft/testfx/pull/2585) - MSTEST0022: Prefer 'TestCleanup' methods over Dispose by [@​Evangelink](https://togithub.com/Evangelink) in [#​2586](https://togithub.com/microsoft/testfx/pull/2586) - MSTEST0023: Do not negate boolean assertions by [@​Evangelink](https://togithub.com/Evangelink) in [#​2594](https://togithub.com/microsoft/testfx/pull/2594) - MSTEST0024: Do not store TestContext in static members by [@​Evangelink](https://togithub.com/Evangelink) in [#​2597](https://togithub.com/microsoft/testfx/pull/2597) If you've just learned about MSTest analyzers, please also check out the [analyzers that were added in previous releases](https://learn.microsoft.com/en-us/dotnet/core/testing/mstest-analyzers/overview). 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](https://www.nuget.org/packages/MSTest/) NuGet meta-package. But can also be installed separately using the [MSTest.Analyzers](https://www.nuget.org/packages/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: ![image](https://togithub.com/microsoft/testfx/assets/5735905/517bd606-36f8-4096-9e30-e8b88580f46c) Alternatively timeouts can be specified through runsettings. For example like this: ```xml 1000 ``` ##### Better errors on data mismatch When you provide data that don't match your test method signature, the test will fail with an informative message, rather than just "Parameter count mismatch.". ![image](https://togithub.com/microsoft/testfx/assets/5735905/d44fd401-a0b9-4959-90ce-8ed24d236361) ![image](https://togithub.com/microsoft/testfx/assets/5735905/b7d478a7-414c-47c2-8322-5bd4c02da8bb) (There is also an analyzer that helps with the same while you are writing the code.) ##### MSTest SDK updates We've introduced MSTest project SDK in [this .NET Blog post](https://devblogs.microsoft.com/dotnet/introducing-mstest-sdk/). ##### Choosing version in global.json In this release we are promoting a way to define the `MSTest.Sdk` version in `global.json`. This makes it easier to specify the version in a single place, instead of in every project. ```json { "msbuild-sdks": { "MSTest.Sdk": "3.4.0" } } ``` ```xml net8.0 ``` ##### Playwright support We've added a property to enable Playwright, to simplify creating web tests: ```xml net8.0 true ``` ##### Aspire testing support Similarly we've added a property to enable Aspire testing: ```xml net8.0 true ``` ##### Central package management [NuGet central package management](https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management) can now be used together with `MSTest.Sdk`. ##### More examples of SDK projects To see more examples of projects using MSTest.Sdk: ##### MSTest runner ##### Simpler banner We've took inspiration from MSBuild and simplified the runner banner, to show the information, on a single line: .NET Testing Platform v1.2.0+3abae95b6 (UTC 2024/05/03) [win-x64 - .NET 8.0.4] ##### STA support and WinUI support The runner can be configured to run in STA (Single Thread Apartment) mode, which is required for running UI tests. And it also supports WinUI workloads. See the examples here: [samples/mstest-runner/MSTestRunnerWinUI](https://togithub.com/microsoft/testfx/tree/main/samples/mstest-runner/MSTestRunnerWinUI) ##### And more And much more, see the complete change log here: https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#3.4.0 ### [`v3.3.1`](https://togithub.com/microsoft/testfx/releases/tag/v3.3.1) See the release notes [here](https://togithub.com/microsoft/testfx/blob/main/docs/Changelog.md#331---2024-04-04) ### [`v3.3.0`](https://togithub.com/microsoft/testfx/releases/tag/v3.3.0) See the release notes [here](https://togithub.com/microsoft/testfx/blob/main/docs/Changelog.md#330---2024-04-23).

Configuration

πŸ“… Schedule: Branch creation - At any time (no schedule defined), 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 these updates again.



This PR has been generated by Mend Renovate. View repository job log here.

codecov[bot] commented 1 month ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 76.1%. Comparing base (3b5dac6) to head (cdc3635).

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #1119 +/- ## ===================================== Coverage 76.1% 76.1% ===================================== Files 255 255 Lines 11306 11306 Branches 1135 1135 ===================================== Hits 8614 8614 Misses 2357 2357 Partials 335 335 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

github-actions[bot] commented 1 month ago

πŸ‘‹ Hi! It looks like you modified some files in the Detectors folder. You may need to bump the detector versions if any of the following scenarios apply:

If none of the above scenarios apply, feel free to ignore this comment πŸ™‚