Bump MSTest.TestAdapter from 2.1.2 to 4.1.0#123
Open
dependabot[bot] wants to merge 1 commit intoadd-code-qlfrom
Open
Conversation
--- updated-dependencies: - dependency-name: MSTest.TestAdapter dependency-version: 4.1.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
158fc0d to
15c59ac
Compare
This file contains hidden or 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
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.
Updated MSTest.TestAdapter from 2.1.2 to 4.1.0.
Release notes
Sourced from MSTest.TestAdapter's releases.
4.1.0
See the release notes here
4.0.2
See the release notes here
4.0.1
See the release notes here
4.0.0
What is new?
Assert.That
MSTest v4 adds a new type of assertion, that allows you to write any expression, and it will inspect the result to give you more information on failure. Providing a very flexible way to assert complicated expressions. Here a simple example:
CallerArgumentExpression
CallerArgumentExpression is consumed by all assertions, to make them aware of the expressions used in the assertion. In the example below, we now know what both the expected and actual values are. But also what value they come from, giving us opportunity to provide better error messages:
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.".
... (truncated)
3.3.1
See the release notes here
3.3.0
See the release notes here.
3.2.2
See the release notes here.
3.2.1
See the release notes here.
3.2.0
See the release notes here.
3.2.0-preview.24069.3
See the release notes here.
3.2.0-preview.23623.1
See the release notes here.
3.2.0-preview.23622.1
See the release notes here.
3.1.1
See the release notes here.
3.1.0
See the release notes here.
ARTIFACTS FOR THIS RELEASE WERE CORRUPTED - YOU NEED TO LOOK AT ARTIFACTS OF v3.1.1
3.0.4
See the release notes here.
3.0.3
See the release notes here.
3.0.2
See the release notes here.
3.0.1
See the release notes here.
3.0.0
See the release notes here.
3.0.0-preview-20221122-01
See the release notes here.
3.0.0-preview-20221110-04
See the release notes here.
Breaking changes
See breaking changes announcement
DataRowAttribute2.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.
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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)