Closed renovate[bot] closed 1 month ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 76.1%. Comparing base (
3b5dac6
) to head (cdc3635
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
π 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:
devDependencies
values than beforeIf none of the above scenarios apply, feel free to ignore this comment π
This PR contains the following updates:
3.2.2
->3.4.0
3.2.2
->3.4.0
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: ```xmlConfiguration
π 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.