chore(deps): update mstest monorepo to v3 (major) #310
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #310 +/- ##
=======================================
Coverage 65.41% 65.41%
=======================================
Files 254 254
Lines 22853 22853
Branches 1938 1938
=======================================
Hits 14949 14949
Misses 7360 7360
Partials 544 544 ☔ View full report in Codecov by Sentry. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.3->3.6.02.2.3->3.6.0Release Notes
microsoft/testfx (MSTest.TestAdapter)
v3.6.0See the release notes here
Special shoutout to @SimonCropp for his exceptional contribution in improving the quality of the repository.
v3.5.2See the release notes here
v3.5.1See the release notes here
v3.5.0See the release notes here
v3.4.3See the release notes here
v3.4.2: v.3.4.2See the release notes here
v3.4.1See the release notes here
v3.4.0Here 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 hasinfoseverity by default, and will show a message, when you storeTestContextin a static member in your class. This is not recommended, and you should be using aTestContextproperty 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.Sdkversion inglobal.json. This makes it easier to specify the version in a single place, instead of in every project.{ "msbuild-sdks": { "MSTest.Sdk": "3.4.0" } }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.1See the release notes here
v3.3.0See the release notes here.
v3.2.2See the release notes here.
v3.2.1See the release notes here.
v3.1.1See the release notes here.
v3.0.4See the release notes here.
v3.0.3See the release notes here.
v3.0.2See the release notes here.
v3.0.1See the release notes here.
v3.0.0See the release notes here.
v2.2.10See release notes here.
v2.2.9Parallel output
MSTest 2.2.9 captures all Console output and attaches it to the correct test, even if you are running tests in parallel. This output is captured from your test code as well as from the tested code. And it requires no special setup.
Before
In 2.2.8, test output is scattered among tests, in our example, one unlucky test gets all the output of other tests just mixed together:
After
With 2.2.9, each output is correctly attached to the test that produced it:
Also notice that we are also capturing debug, trace and error. And we are not awaiting the FastChild method, and the output is still assigned correctly. Souce code.
Limitations
Due to the way that class and assembly initialize, and cleanup are invoked, their output will end up in the first test that run (or last for cleanup). This is unfortunately not easily fixable.
See release notes here.
v2.2.8See release notes here.
v2.2.7See release notes here.
v2.2.6See release notes here.
v2.2.5See release notes here.
v2.2.4See 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.