chore(deps): update test tooling packages

Aberta
  • Algo errado?
#590 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
55/100
Tipo de issue
Refatoração
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
csharp, docker, github-actions
Domínio
devops, testing

Direção de pesquisa

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

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
C#
Estrelas
184
Forks
48
Merge médio
21min
PRs com merge (30d)
7

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de CommunityToolkit/Datasync

Todas as issues de CommunityToolkit/Datasync

Issues semelhantes

Mais issues de C#

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.