chore(deps): update test tooling packages

Aperta
  • Qualcosa non va?
#590 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
55/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
csharp, docker, github-actions
Ambito
devops, testing

Direzione di ricerca

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/.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
C#
Stelle
184
Fork
48
Merge medio
21m
PR unite (30g)
7

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CommunityToolkit/Datasync

Tutte le issue di CommunityToolkit/Datasync

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.