Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update mstest monorepo to v3 (major) #1111

Merged
merged 2 commits into from
Feb 16, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 16, 2024

Mend Renovate

This PR contains the following updates:

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

Release Notes

microsoft/testfx (MSTest.TestAdapter)

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.

v2.2.10

See release notes here.

v2.2.9

Parallel output

🙇 Shout out to @​SimonCropp, for bringing this functionality to XUnit in his https://github.com/SimonCropp/XunitContext project. And being an inspiration for implementing this.

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:

image

After

With 2.2.9, each output is correctly attached to the test that produced it:

image
image

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.


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.


  • If you want to rebase/retry this PR, check this box

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

@renovate renovate bot force-pushed the renovate/major-mstest-monorepo branch from 580d884 to ebd8a58 Compare February 16, 2024 23:49
@renovate renovate bot force-pushed the renovate/major-mstest-monorepo branch from ebd8a58 to 7d09a73 Compare February 16, 2024 23:50
@ChrisPulman ChrisPulman enabled auto-merge (squash) February 16, 2024 23:50
@renovate renovate bot force-pushed the renovate/major-mstest-monorepo branch from 7d09a73 to 97fd9a6 Compare February 16, 2024 23:55
@glennawatson glennawatson merged commit de14096 into main Feb 16, 2024
1 check failed
@glennawatson glennawatson deleted the renovate/major-mstest-monorepo branch February 16, 2024 23:59
Copy link

github-actions bot commented Mar 2, 2024

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants