Update mstest monorepo to v3 (major) #21
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.2.10
->3.7.0
2.2.10
->3.7.0
Release Notes
microsoft/testfx (MSTest.TestAdapter)
v3.7.0
See the release notes here
v3.6.4
See the release notes here
v3.6.3
See the release notes here
v3.6.2
See the release notes here
v3.6.1
See the release notes here
v3.6.0
See the release notes here
Special shoutout to @SimonCropp for his exceptional contribution in improving the quality of the repository.
v3.5.2
See the release notes here
v3.5.1
See the release notes here
v3.5.0
See the release notes here
v3.4.3
See the release notes here
v3.4.2
: v.3.4.2See 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:
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:
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:
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.".
(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.
Choosing version in global.json
In this release we are promoting a way to define the
MSTest.Sdk
version inglobal.json
. This makes it easier to specify the version in a single place, instead of in every project.Playwright support
We've added a property to enable Playwright, to simplify creating web tests:
Aspire testing support
Similarly we've added a property to enable Aspire testing:
Central package management
NuGet 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:
https://github.com/microsoft/testfx/tree/rel/3.4/samples/public/DemoMSTestSdk
MSTest runner
Simpler banner
We've took inspiration from MSBuild and simplified the runner banner, to show the information, on a single line:
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 MSTestRunnerWinUI example
And more
And much more, see the complete change log here: https://github.com/microsoft/testfx/blob/main/docs/Changelog.md#3.4.0
New Contributors
A special thank you to all our new contributors:
v3.3.1
See the release notes here
v3.3.0
See the release notes here.
v3.2.2
See the release notes here.
v3.2.1
See the release notes here.
v3.1.1
See the release notes here.
v3.0.4
See the release notes here.
v3.0.3
See the release notes here.
v3.0.2
See the release notes here.
v3.0.1
See the release notes here.
v3.0.0
See the release notes here.
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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR was generated by Mend Renovate. View the repository job log.