search

samsmithnz / ResearchTree

An experiment to see if I can build a research tree
0 stars 0 forks source link

Bump the tests group across 1 directory with 3 updates #92

Closed dependabot[bot] closed 5 months ago

dependabot[bot] commented 5 months ago

Bumps the tests group with 3 updates in the /src/ResearchTree.Tests directory: Microsoft.NET.Test.Sdk, MSTest.TestAdapter and MSTest.TestFramework.

Updates Microsoft.NET.Test.Sdk from 17.9.0 to 17.10.0

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

v17.10.0

What's Changed

And many infrastructure related changes and updates.

New Contributors

Full Changelog: https://github.com/microsoft/vstest/compare/v17.9.0...v17.10.0

v17.10.0-release-24177-07

What's Changed

... (truncated)

Commits


Updates MSTest.TestAdapter from 3.3.1 to 3.4.3

Release notes

Sourced from MSTest.TestAdapter's releases.

v3.4.3

See the release notes here

v.3.4.2

See the release notes here

v3.4.1

See the release notes here

v3.4.0

Here are the highlights of the current release, full change log is available below:

https://github.com/microsoft/testfx/compare/v3.3.1...v3.4.0

MSTest

New and improved analyzers

We've added more code analyzers to help you prevent mistakes, and to ensure a consistent code style of your tests.

One example of a new analyzer that was added in 3.4.0 is MSTEST0024: Do not store TestContext in static members. This analyzer has info severity by default, and will show a message, when you store TestContext in a static member in your class. This is not recommended, and you should be using a TestContext property instead:

image

The other analyzers added in this release:

If you've just learned about MSTest analyzers, please also check out the analyzers that were added in previous releases. They will help you ensure that your test classes and test methods are recognized by MSTest and are not accidentally ignored.

The analyzers are automatically installed with the MSTest NuGet meta-package. But can also be installed separately using the MSTest.Analyzers NuGet package.

More timeout options

Timeout can now be specified on all fixture methods, including ClassCleanup, AssemblyCleanup, TestCleanup and TestInitalize. In this case I want my [ClassCleanup] to time out after 1 second:

image

Alternatively timeouts can be specified through runsettings. For example like this:

<RunSettings>
  <MSTest>
</tr></table>

... (truncated)

Changelog

Sourced from MSTest.TestAdapter's changelog.

[3.4.3] - 2024-05-30

See full log here

Fixed

Artifacts

  • MSTest: 3.4.3
  • MSTest.TestFramework: 3.4.3
  • MSTest.TestAdapter: 3.4.3
  • MSTest.Analyzers: 3.4.3
  • MSTest.Sdk: 3.4.3
  • Microsoft.Testing.Extensions.CrashDump: 1.2.1
  • Microsoft.Testing.Extensions.HangDump: 1.2.1
  • Microsoft.Testing.Extensions.HotReload: 1.2.1
  • Microsoft.Testing.Extensions.Retry: 1.2.1
  • Microsoft.Testing.Extensions.TrxReport: 1.2.1

[3.4.2] - 2024-05-30

See full log here

Fixed

Artifacts

  • MSTest: 3.4.2
  • MSTest.TestFramework: 3.4.2
  • MSTest.TestAdapter: 3.4.2
  • MSTest.Analyzers: 3.4.2
  • MSTest.Sdk: 3.4.2
  • Microsoft.Testing.Extensions.CrashDump: 1.2.1
  • Microsoft.Testing.Extensions.HangDump: 1.2.1
  • Microsoft.Testing.Extensions.HotReload: 1.2.1
  • Microsoft.Testing.Extensions.Retry: 1.2.1
  • Microsoft.Testing.Extensions.TrxReport: 1.2.1

[3.4.1] - 2024-05-27

See full log here

Fixed

... (truncated)

Commits


Updates MSTest.TestFramework from 3.3.1 to 3.4.3

Release notes

Sourced from MSTest.TestFramework's releases.

v3.4.3

See the release notes here

v.3.4.2

See the release notes here

v3.4.1

See the release notes here

v3.4.0

Here are the highlights of the current release, full change log is available below:

https://github.com/microsoft/testfx/compare/v3.3.1...v3.4.0

MSTest

New and improved analyzers

We've added more code analyzers to help you prevent mistakes, and to ensure a consistent code style of your tests.

One example of a new analyzer that was added in 3.4.0 is MSTEST0024: Do not store TestContext in static members. This analyzer has info severity by default, and will show a message, when you store TestContext in a static member in your class. This is not recommended, and you should be using a TestContext property instead:

image

The other analyzers added in this release:

If you've just learned about MSTest analyzers, please also check out the analyzers that were added in previous releases. They will help you ensure that your test classes and test methods are recognized by MSTest and are not accidentally ignored.

The analyzers are automatically installed with the MSTest NuGet meta-package. But can also be installed separately using the MSTest.Analyzers NuGet package.

More timeout options

Timeout can now be specified on all fixture methods, including ClassCleanup, AssemblyCleanup, TestCleanup and TestInitalize. In this case I want my [ClassCleanup] to time out after 1 second:

image

Alternatively timeouts can be specified through runsettings. For example like this:

<RunSettings>
  <MSTest>
</tr></table>

... (truncated)

Changelog

Sourced from MSTest.TestFramework's changelog.

[3.4.3] - 2024-05-30

See full log here

Fixed

Artifacts

  • MSTest: 3.4.3
  • MSTest.TestFramework: 3.4.3
  • MSTest.TestAdapter: 3.4.3
  • MSTest.Analyzers: 3.4.3
  • MSTest.Sdk: 3.4.3
  • Microsoft.Testing.Extensions.CrashDump: 1.2.1
  • Microsoft.Testing.Extensions.HangDump: 1.2.1
  • Microsoft.Testing.Extensions.HotReload: 1.2.1
  • Microsoft.Testing.Extensions.Retry: 1.2.1
  • Microsoft.Testing.Extensions.TrxReport: 1.2.1

[3.4.2] - 2024-05-30

See full log here

Fixed

Artifacts

  • MSTest: 3.4.2
  • MSTest.TestFramework: 3.4.2
  • MSTest.TestAdapter: 3.4.2
  • MSTest.Analyzers: 3.4.2
  • MSTest.Sdk: 3.4.2
  • Microsoft.Testing.Extensions.CrashDump: 1.2.1
  • Microsoft.Testing.Extensions.HangDump: 1.2.1
  • Microsoft.Testing.Extensions.HotReload: 1.2.1
  • Microsoft.Testing.Extensions.Retry: 1.2.1
  • Microsoft.Testing.Extensions.TrxReport: 1.2.1

[3.4.1] - 2024-05-27

See full log here

Fixed

... (truncated)

Commits


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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will 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 minor version` will 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 ` 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 ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions