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 v2.2.10 #8

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 25, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
MSTest.TestAdapter 2.2.3 -> 2.2.10 age adoption passing confidence
MSTest.TestAdapter 2.1.1 -> 2.2.10 age adoption passing confidence
MSTest.TestFramework 2.2.3 -> 2.2.10 age adoption passing confidence
MSTest.TestFramework 2.1.1 -> 2.2.10 age adoption passing confidence

Release Notes

microsoft/testfx (MSTest.TestAdapter)

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.

v2.2.8

See release notes here.

v2.2.7

See release notes here.

v2.2.6

See release notes here.

v2.2.5

See release notes here.

v2.2.4

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 changed the title chore(deps): update mstest monorepo to v2.2.9 chore(deps): update mstest monorepo to v2.2.10 Apr 26, 2022
@renovate renovate bot force-pushed the renovate/mstest-monorepo branch from edf9964 to d3ece69 Compare April 26, 2022 14:18
@renovate renovate bot changed the title chore(deps): update mstest monorepo to v2.2.10 Update mstest monorepo to v2.2.10 Dec 17, 2022
@renovate renovate bot changed the title Update mstest monorepo to v2.2.10 chore(deps): update mstest monorepo to v2.2.10 Dec 17, 2022
@renovate renovate bot force-pushed the renovate/mstest-monorepo branch from f870048 to df449ec Compare March 16, 2023 07:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants