fix(stryker): Fix test-mutations workflow to use dotnet tool restore

[piotrzajac]

Summary

Fix test-mutations workflow to use dotnet tool restore

Summary by CodeRabbit

• Documentation

  • Added backlog task documenting CI workflow improvements.

• Chores

  • Simplified .NET tools restoration in the CI pipeline, replacing manual setup with automated tool restoration for improved build consistency.

Checklist

• Commit messages follow Conventional Commits (type(scope): description)
• dotnet build src/Objectivity.AutoFixture.XUnit2.AutoMock.sln passes with no warnings
• dotnet test src/Objectivity.AutoFixture.XUnit2.AutoMock.sln passes on all framework slices
• Code coverage remains at least at the level prior the change (verified by Codecov)
• Mutation score remains at least at the level prior the change (verified by Stryker)
• New tests follow the GIVEN/WHEN/THEN naming convention and AAA structure (see AGENTS.md)
• No new [SuppressMessage] without a justification comment
• No // TODO: comments added — open a GitHub issue instead
• No new dependencies introduced that are incompatible with the MIT license (verified by FOSSA)

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d6c6068d-a4da-42af-9672-cfaa81b2246d

📥 Commits

Reviewing files that changed from the base of the PR and between dcb4f2a and 4379cc5.

📒 Files selected for processing (2)

• .backlog/tasks/task-9 - Fix-test-mutations-workflow-to-use-dotnet-tool-restore.md
• .github/workflows/test-mutations.yml

---

📝 Walkthrough

Walkthrough

The CI workflow for mutation testing is refactored to use dotnet tool restore instead of manually creating a tool manifest and installing the dotnet-stryker tool. A backlog task document is added to track this change.

Changes

Cohort / File(s)	Summary
CI Workflow Optimization .github/workflows/test-mutations.yml	Replaced multi-step tool installation (create manifest, install tool) with single dotnet tool restore command that sources tools from repository-level dotnet-tools.json manifest.
Backlog/Task Documentation .backlog/tasks/task-9 - Fix-test-mutations-workflow-to-use-dotnet-tool-restore.md	Added new task document outlining the CI workflow fix, including acceptance criteria and implementation plan for switching to dotnet tool restore.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Enforce conventional commits #305: Similar CI/tooling update to use repository-local dotnet-tools.json and dotnet tool restore for managing .NET tools.

Suggested labels

enhancement

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is missing a link to the related issue (Closes #) and lacks details about the implementation. While the checklist is marked complete, required context about what issue this PR addresses is absent.	Add 'Closes #<issue_number>' to reference the related issue and provide a brief explanation of the workflow changes being made.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: updating the test-mutations workflow to use dotnet tool restore instead of the previous multi-step approach.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/test-mutations-workflow-should-use-dotnet-tool-restore

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[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 (071c4e8) to head (4379cc5).
⚠️ Report is 3 commits behind head on master.
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #314   +/-   ##
=========================================
  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.

[piotrzajac]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.