Bump the test-stack group with 1 update - #10
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps Microsoft.Testing.Extensions.TrxReport from 1.9.1 to 2.3.3 --- updated-dependencies: - dependency-name: Microsoft.Testing.Extensions.TrxReport dependency-version: 2.3.3 dependency-type: direct:production update-type: version-update:semver-major dependency-group: test-stack ... Signed-off-by: dependabot[bot] <support@github.com>
|
Closing — verified broken, both locally and in CI. The bump restores and compiles with zero warnings, then fails at run time:
That last part is why this one matters more than an ordinary red build: no TRX is what the mutation harness reports as inconclusive rather than as a failure. This is the shape of breakage that is easiest to wave through and hardest to notice afterwards.
|
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Updated Microsoft.Testing.Extensions.TrxReport from 1.9.1 to 2.3.3.
Release notes
Sourced from Microsoft.Testing.Extensions.TrxReport's releases.
2.3.0-preview-20220810-02
See release notes here.
2.2.10
See release notes here.
2.2.10-preview-20220414-01
See release notes here.
2.2.9
Parallel 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.
2.2.8
See release notes here.
2.2.7
See release notes here.
2.2.6
See release notes here.
2.2.5
See release notes here.
2.2.4
See release notes here.
2.2.4-preview-20210331-02
See release notes here.
2.2.3
See release notes here.
2.2.2
See release notes here.
2.2.1
See release notes here.
2.2.0-preview-20210115-03
See release notes here.
2.2.0-preview-20201126-03
See release notes here.
2.1.2
See release notes here.
2.1.1
See release notes here.
2.1.0
See release notes here.
2.1.0-beta2
See release notes here
2.1.0-beta
See release notes here
2.0.0
2.0.0-beta4
2.0.0-beta2
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions