Update xunit.runner

[piotrzajac]

Summary by CodeRabbit

• Chores
  • Updated the test projects to use the latest version of the xUnit Visual Studio runner (3.1.0).

[coderabbitai]

Walkthrough

The changes update the xunit.runner.visualstudio NuGet package reference from version 3.0.2 to 3.1.0 across four test project files. No other modifications to dependencies, code, or project configuration were made.

Changes

Files

Change Summary

src/Objectivity.AutoFixture.XUnit2.AutoFakeItEasy.Tests/Objectivity.AutoFixture.XUnit2.AutoFakeItEasy.Tests.csproj src/Objectivity.AutoFixture.XUnit2.AutoMoq.Tests/Objectivity.AutoFixture.XUnit2.AutoMoq.Tests.csproj src/Objectivity.AutoFixture.XUnit2.AutoNSubstitute.Tests/Objectivity.AutoFixture.XUnit2.AutoNSubstitute.Tests.csproj src/Objectivity.AutoFixture.XUnit2.Core.Tests/Objectivity.AutoFixture.XUnit2.Core.Tests.csproj

Updated xunit.runner.visualstudio NuGet package from 3.0.2 to 3.1.0

Suggested labels

dependencies, .NET

Poem

A hop, a skip, a version bump,
The test runners get a gentle jump.
From 3.0.2 to 3.1.0 we go,
With carrots in paw, we watch tests flow.
🥕✨

— A rabbit who loves a tidy dependency row

Tip

⚡️ Faster reviews with caching

• CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.

Enjoy the performance boost—your workflow just got faster.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7ae069c and 4982b5a.

📒 Files selected for processing (4)

• src/Objectivity.AutoFixture.XUnit2.AutoFakeItEasy.Tests/Objectivity.AutoFixture.XUnit2.AutoFakeItEasy.Tests.csproj (1 hunks)
• src/Objectivity.AutoFixture.XUnit2.AutoMoq.Tests/Objectivity.AutoFixture.XUnit2.AutoMoq.Tests.csproj (1 hunks)
• src/Objectivity.AutoFixture.XUnit2.AutoNSubstitute.Tests/Objectivity.AutoFixture.XUnit2.AutoNSubstitute.Tests.csproj (1 hunks)
• src/Objectivity.AutoFixture.XUnit2.Core.Tests/Objectivity.AutoFixture.XUnit2.Core.Tests.csproj (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (7)

• GitHub Check: build-test-pack (Core) / run
• GitHub Check: build-test-pack (AutoNSubstitute) / run
• GitHub Check: build-test-pack (AutoFakeItEasy) / run
• GitHub Check: build-test-pack (AutoMoq) / run
• GitHub Check: scan
• GitHub Check: scan (csharp)
• GitHub Check: test

🔇 Additional comments (5)

src/Objectivity.AutoFixture.XUnit2.AutoFakeItEasy.Tests/Objectivity.AutoFixture.XUnit2.AutoFakeItEasy.Tests.csproj (1)

104-107: Approve version bump for xunit.runner.visualstudio

The xunit.runner.visualstudio package has been correctly updated from 3.0.2 to 3.1.0, matching the other test projects in the solution. No compatibility concerns with Microsoft.NET.Test.Sdk 17.13.0 have been identified.

src/Objectivity.AutoFixture.XUnit2.Core.Tests/Objectivity.AutoFixture.XUnit2.Core.Tests.csproj (1)

103-106:

Details

❓ Verification inconclusive

Upgrade xunit.runner.visualstudio to 3.1.0

The version bump to 3.1.0 ensures you’re using the latest test runner with all recent fixes. Please verify that:

• Version 3.1.0 exists on NuGet and is compatible with all target frameworks (net8.0, net472, net48).
• No breaking changes in test discovery or execution have been introduced.
• All other test projects in the repo reference the same 3.1.0 version to avoid inconsistencies.

Run the full test suite and confirm consistent package references:

---

🏁 Script executed:

#!/bin/bash
# Verify xunit.runner.visualstudio version across all test projects
rg -n "<PackageReference Include=\"xunit.runner.visualstudio\"" -A 1

Length of output: 1429

---

Uniform xunit.runner.visualstudio Version 3.1.0 across all test projects

We’ve confirmed via ripgrep that every test project now references xunit.runner.visualstudio 3.1.0:

• src/Objectivity.AutoFixture.XUnit2.Core.Tests/Objectivity.AutoFixture.XUnit2.Core.Tests.csproj
• src/Objectivity.AutoFixture.XUnit2.AutoMoq.Tests/Objectivity.AutoFixture.XUnit2.AutoMoq.Tests.csproj
• src/Objectivity.AutoFixture.XUnit2.AutoFakeItEasy.Tests/Objectivity.AutoFixture.XUnit2.AutoFakeItEasy.Tests.csproj
• src/Objectivity.AutoFixture.XUnit2.AutoNSubstitute.Tests/Objectivity.AutoFixture.XUnit2.AutoNSubstitute.Tests.csproj

Please verify that:

• Version 3.1.0 is available on nuget.org and supports all target frameworks (net8.0, net472, net48).
• There are no breaking changes in test discovery or execution by running the full test suite locally.

src/Objectivity.AutoFixture.XUnit2.AutoMoq.Tests/Objectivity.AutoFixture.XUnit2.AutoMoq.Tests.csproj (2)

105-108: Approve package reference update
The bump of xunit.runner.visualstudio from 3.0.2 to 3.1.0 looks correct and aligns with the updates in the other test projects. No breaking changes are anticipated for this minor version upgrade.

---

105-108:

Details

✅ Verification successful

Verify no remaining outdated references
Ensure that all test project files have been updated and there are no lingering references to the old 3.0.2 version. Run the following script from the repo root; it should produce zero matches:

---

🏁 Script executed:

#!/usr/bin/env bash
# Search for any csproj still referencing xunit.runner.visualstudio version 3.0.2
rg -n '<PackageReference\s+Include="xunit\.runner\.visualstudio".*Version="3\.0\.2"' -g '*.csproj'

Length of output: 100

---

🏁 Script executed:

#!/usr/bin/env bash
# List all csproj files referencing xunit.runner.visualstudio (any version)
rg -n '<PackageReference\s+Include="xunit\.runner\.visualstudio"' -g '*.csproj'
# List any csproj still referencing version 3.0.2
rg -n 'Version="3\.0\.2"' -g '*.csproj'

Length of output: 867

---

No remaining 3.0.2 references found

All test projects now reference xunit.runner.visualstudio version 3.1.0 and no csproj files include version 3.0.2.

Affected files:

• src/Objectivity.AutoFixture.XUnit2.Core.Tests/Objectivity.AutoFixture.XUnit2.Core.Tests.csproj (line 103)
• src/Objectivity.AutoFixture.XUnit2.AutoMoq.Tests/Objectivity.AutoFixture.XUnit2.AutoMoq.Tests.csproj (line 105)
• src/Objectivity.AutoFixture.XUnit2.AutoNSubstitute.Tests/Objectivity.AutoFixture.XUnit2.AutoNSubstitute.Tests.csproj (line 104)
• src/Objectivity.AutoFixture.XUnit2.AutoFakeItEasy.Tests/Objectivity.AutoFixture.XUnit2.AutoFakeItEasy.Tests.csproj (line 104)

All clear.

src/Objectivity.AutoFixture.XUnit2.AutoNSubstitute.Tests/Objectivity.AutoFixture.XUnit2.AutoNSubstitute.Tests.csproj (1)

104-107: Bump xunit.runner.visualstudio to v3.1.0
Updated the xunit.runner.visualstudio package from 3.0.2 to 3.1.0 as intended by the PR. This aligns with the other test projects and should work across all targeted frameworks.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (7ae069c) to head (4982b5a).

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #258   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           39        39           
  Lines          424       424           
  Branches        55        55           
=========================================
  Hits           424       424           

Flag	Coverage Δ
unittests	99.76% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

Qodana Community for .NET

Analyzed project: src/

It seems all right 👌

No new problems were found according to the checks applied

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/[email protected]
        with:
          upload-result: true

Contact Qodana team

Contact us at [email protected]

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions