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:
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 hasinfo
severity by default, and will show a message, when you storeTestContext
in a static member in your class. This is not recommended, and you should be using aTestContext
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 #2799If 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)
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 #3048Artifacts
- 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 #3034Artifacts
- 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)
27aa72e
Revert version of Code Coverage to 17.10.4 (#3048)1225aed
Update Versions.propsa502340
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.1bafa77b
Use VSTest 17.10 (#2902)7fd9f76
Use latest version of TA and MSTest.Engine (#2885)