chore(deps): update test tooling packages

Open
  • Is something wrong?
#590 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp, docker, github-actions
Domain
devops, testing

Research direction

Update the package versions and TestContainersVersion in the root Directory.Packages.props, first verifying each target on NuGet. Read the dotnet test step in .github/workflows/build-library.yml to confirm how coverage is collected, then run restore, build, and tests with Docker running. Done when local and fork CI succeed and coverage reports appear in TestResults/.

Written by the indexing model from the issue text.

Description

dependencies Infrastructure

Part 4 of the outdated-package sweep (dotnet-outdated 4.8.1, 2026-11-05). Minor version updates for test tooling only. No shipped package changes.

Scope (this PR only)

Root Directory.Packages.props:

Package Current Target Notes
Microsoft.NET.Test.Sdk 18.6.0 18.11.0
AwesomeAssertions 9.4.0 9.6.0 Check release notes for new analyzer warnings (build treats code style as errors via EnforceCodeStyleInBuild).
coverlet.collector 10.0.1 10.1.0 Keep in lockstep with coverlet.msbuild.
coverlet.msbuild 10.0.1 10.1.0
<TestContainersVersion> (TestContainers.MongoDb / MsSql / PostgreSql) 4.12.0 4.16.0 Single property drives all three. Requires Docker locally.
XUnit.Combinatorial 2.0.24 2.1.43 Only needs xunit.v3.extensibility.core >= 1.0.0, so it works on xunit.v3 3.x and 4.x. Keep the existing explanatory comment accurate.

Verify versions on NuGet first (https://api.nuget.org/v3-flatcontainer/<lowercase-id>/index.json).

Out of scope: xunit.v3*, xunit.runner.visualstudio (separate xUnit 4 issue), NSubstitute (separate issue), System.Linq.Async and Microsoft.AspNetCore.Mvc.Testing (covered by the patch PR).

Steps

  1. Edit props.
  2. dotnet restore && dotnet build && dotnet test (Docker running). Confirm coverage still produces TestResults/ output as the CI workflow expects (see the dotnet test step in .github/workflows/build-library.yml: it uses coverlet / XPlat Code Coverage).
  3. Dispatch build-library.yml on the fork with --ref <branch>; confirm the test summary and coverage steps succeed.

Acceptance criteria

  • Packages at target versions; local and CI green; coverage reports still generated.
  • PR title: chore(deps): update test tooling packages.
Dominant language
C#
Stars
184
Forks
48
Avg merge
21m
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CommunityToolkit/Datasync

All issues in CommunityToolkit/Datasync

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.