chore(deps): update test tooling packages

Abierto
  • ¿Algo no está bien?
#590 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
55/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp, docker, github-actions
Área
devops, testing

Línea de trabajo

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

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.
Lenguaje dominante
C#
Estrellas
184
Forks
48
Merge medio
21 min
PR fusionados (30 d)
7

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de CommunityToolkit/Datasync

Todos los issues de CommunityToolkit/Datasync

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.