Migrate test project from VSTest to Microsoft Testing Platform - #101
Conversation
Switch SIL.Harmony.Tests to run on Microsoft.Testing.Platform (MTP) instead of VSTest, following the .NET VSTest-to-MTP migration guidance. - Enable the MTP runner for the xUnit.net v3 test project (UseMicrosoftTestingPlatformRunner + OutputType=Exe). - Use the xunit.v3.mtp-v2 package so the GitHubActionsTestLogger MTP extension (which requires MTP v2) can report results in CI. - Add global.json with test.runner=Microsoft.Testing.Platform so `dotnet test` uses MTP on the .NET 10 SDK. - Remove VSTest-only packages: Microsoft.NET.Test.Sdk, xunit.runner.visualstudio, coverlet.collector, and the explicit Microsoft.Testing.Platform reference (now transitive). - Update CI workflows to replace the VSTest `--logger GitHubActions` with the MTP `--report-github` flag. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PKdgdJdeDQrwFE5pruMH3n
|
Warning Review limit reached
Next review available in: 59 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe test projects now use Microsoft Testing Platform with the xUnit v3 MTP runner. Central test dependencies were updated, and both CI workflows now use ChangesTest platform migration
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
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. Comment |
…st-to-mtp-klhckk # Conflicts: # Directory.Packages.props
With central transitive pinning enabled (merged from main), the pin must be >= 2.0.2 to satisfy xunit.v3.core.mtp-v2 3.2.2; 2.0.0 caused an NU1109 package downgrade error on restore. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PKdgdJdeDQrwFE5pruMH3n
Switch to the fancy new MTP test runner, instead of vs test.
AI Summary
Switch SIL.Harmony.Tests to run on Microsoft.Testing.Platform (MTP) instead of VSTest, following the .NET VSTest-to-MTP migration guidance.
dotnet testuses MTP on the .NET 10 SDK.--logger GitHubActionswith the MTP--report-githubflag.Claude-Session: https://claude.ai/code/session_01PKdgdJdeDQrwFE5pruMH3n
Summary by CodeRabbit