Bump xunit.runner.visualstudio from 2.4.3 to 2.4.5

[dependabot]

Bumps xunit.runner.visualstudio from 2.4.3 to 2.4.5.

Release notes

Sourced from xunit.runner.visualstudio's releases.

v2.4.4.1

Changes:

Bugs:

• #292: Fixing a hang in test discovery

Others:

• #304: Update xunit version to 2.4.2-pre.12
• #297: Bump NSubstitute from 4.2.2 to 4.3.0
• #294: Bump Microsoft.NET.Test.Sdk from 16.10.0 to 17.0.0
• #293: Bump Nerdbank.GitVersioning from 3.4.231 to 3.4.255
• #296: Bump Microsoft.NETCore.UniversalWindowsPlatform from 6.2.12 to 6.2.13
• #299: Bump MSBuild.Sdk.Extras from 3.0.23 to 3.0.44
• #270: Upgrade to GitHub-native Dependabot

• #281: Bump Nerdbank.GitVersioning from 3.4.228 to 3.4.231
• #280: Bump Nerdbank.GitVersioning from 3.4.220 to 3.4.228
• #277: Bump Nerdbank.GitVersioning from 3.4.216 to 3.4.220
• #275: Bump Nerdbank.GitVersioning from 3.4.205 to 3.4.216
• #274: Bump Nerdbank.GitVersioning from 3.4.203 to 3.4.205
• #273: Bump Microsoft.NET.Test.Sdk from 16.9.4 to 16.10.0
• #272: Bump Microsoft.TestPlatform.ObjectModel from 16.9.4 to 16.10.0
• #271: Bump Nerdbank.GitVersioning from 3.4.194 to 3.4.203
• #268: Bump Nerdbank.GitVersioning from 3.4.190 to 3.4.194
• #267: Bump Nerdbank.GitVersioning from 3.3.37 to 3.4.190
• #265: Bump Microsoft.NET.Test.Sdk from 16.9.1 to 16.9.4
• #264: Bump Microsoft.TestPlatform.ObjectModel from 16.9.1 to 16.9.4
• #260: Bump Microsoft.TestPlatform.ObjectModel from 16.8.3 to 16.9.1
• #261: Bump Microsoft.NET.Test.Sdk from 16.8.3 to 16.9.1
• #258: Bump Microsoft.NETCore.UniversalWindowsPlatform from 6.2.11 to 6.2.12
• #256: Bump MSBuild.Sdk.Extras from 3.0.22 to 3.0.23
• #255: Bump MSBuild.Sdk.Extras from 2.1.2 to 3.0.22
• #254: Bump Microsoft.TestPlatform.ObjectModel from 16.8.0 to 16.8.3
• #253: Bump Microsoft.NET.Test.Sdk from 16.8.0 to 16.8.3
• #250: Bump Microsoft.NETCore.UniversalWindowsPlatform from 6.2.10 to 6.2.11
• #246: Bump Microsoft.TestPlatform.ObjectModel from 16.7.0 to 16.8.0
• #245: Bump Microsoft.NET.Test.Sdk from 16.6.1 to 16.8.0
• #240: Bump Nerdbank.GitVersioning from 3.2.31 to 3.3.37
• #231: Bump Microsoft.TestPlatform.ObjectModel from 16.6.1 to 16.7.0

This list of changes was auto generated.

Commits

• See full diff 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 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 ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[TravisEz13]

@dependabot rebase

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.csproj : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detetcted.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[ghost]

🎉v7.3.0-preview.4 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes