Bump MSTest.TestAdapter from 2.2.8 to 4.2.3#17
Conversation
--- updated-dependencies: - dependency-name: MSTest.TestAdapter dependency-version: 4.2.3 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
8da58cf to
f605005
Compare
|
Tried the minimal local fix path before merging. I combined this adapter bump with #18 so both MSTest packages were at 4.2.3, restored and built locally, and the test project still failed at execution time on net6.0 with Method not found: 'System.Nullable<System.Boolean> Microsoft.VisualStudio.TestPlatform.ObjectModel.Utilities.AssemblyHelper.DoesReferencesAssembly(...)'. I also tried newer Microsoft.NET.Test.Sdk versions, but current 17.14.1 and 18.7.0 builds now reject net6.0 outright. Closing this because the repo's current net6.0 test stack is not compatible with MSTest 4.x without a broader framework/test-platform upgrade. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Updated MSTest.TestAdapter from 2.2.8 to 4.2.3.
Release notes
Sourced from MSTest.TestAdapter's releases.
4.2.3
See the release notes here
4.2.2
See the release notes here
4.2.1
See the release notes here
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.
Commits viewable in compare view.