test: flaky integration tests when GetRandomMovie() returns a soft-deleted movie
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 78/100
Línea de trabajo
Empieza con GetRandomMovie() en los dos archivos ServiceApplicationFactory.cs mencionados y compara cómo selecciona cada uno las películas válidas. Excluye las entradas eliminadas de forma lógica en ambas implementaciones y luego ejecuta las pruebas de integración afectadas del cliente y del servidor; la tarea estará terminada cuando la selección aleatoria no pueda devolver una película eliminada de forma lógica y esas pruebas pasen.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
Several integration tests are intermittently flaky because GetRandomMovie() can return a movie that an earlier test in the same class has already soft-deleted and never restored.
Observed failure, from PR #599 (Build and Test Library, run 42093778343). The change in that PR is unrelated, and the identical commit passed on a fork run:
CommunityToolkit.Datasync.Client.Test.Service.Integration_Tests.Read_SoftDeleted_NotDeleted_Returns200 [FAIL]
CommunityToolkit.Datasync.Client.DatasyncHttpException : Gone
at ServiceResponse.ThrowIfNotSuccessful(...)
at DatasyncServiceClient`1.GetAsync(String id, ...)
at Integration_Tests.Read_SoftDeleted_NotDeleted_Returns200() line 152
Root cause
- Each test class that uses the in-memory test server creates one
ServiceApplicationFactoryviaIClassFixture<ServiceApplicationFactory>. All tests in the class share one in-memory movie repository. GetRandomMovie()picks a random movie that satisfiesIsValid(...)(title, year and duration). It does not exclude movies whereDeleted == true.- Several tests soft-delete a random movie, either with
SoftDelete(existingMovie)or throughDELETE api/in-memory/softmovies/{id}. They never restore it. - If a later test in the same class randomly picks one of those movies and calls the
softmoviesendpoint, the server correctly returns410 Gone(or the test's other expectations break), and the test fails.
The failure rate is low and depends on test ordering. A few leaked soft-deleted rows sit in the set of seeded valid movies, so it is probably in the low single-digit percent range per run. That is why it only appears occasionally in CI.
I could not reproduce it locally. 15 consecutive runs of Service.Integration_Tests all passed.
Affected tests
Any test that calls GetRandomMovie() and expects a non-deleted movie, in a class that also soft-deletes movies. The soft-deleting tests also mutate Deleted state themselves.
tests/CommunityToolkit.Datasync.Client.Test
Service/Integration_Tests.cssoft-deletes inCreate_SoftDeleted_Returns409,Read_SoftDeleted_Deleted_Returns404,Read_SoftDeleted_Deleted_WithIncludeDeleted_Returns200,Delete_NotSoftDeleted_Returns204andDelete_SoftDeletedId_Returns410. All 16GetRandomMovie()call sites in that file are exposed.
tests/CommunityToolkit.Datasync.Server.Test has the same GetRandomMovie() implementation in Helpers/ServiceApplicationFactory.cs, and the same soft-delete pattern:
Service/Read_Tests.cs:Read_SoftDeleted_Deleted_Returns410andRead_SoftDeleted_Deleted_WithIncludeDeleted_Returns200.Read_SoftDeleted_NotDeleted_Returns200has the same signature as the observed failure.Service/Delete_Tests.cs:Delete_NotSoftDeleted_Returns204andDelete_SoftDeletedId_Returns410.Service/Replace_Tests.cs: three soft-delete tests.Service/Create_Tests.cs: one soft-delete test.
Suggested fix
Smallest fix: exclude soft-deleted movies in both GetRandomMovie() implementations:
repository.GetEntities().Where(x => IsValid(x) && !x.Deleted).ToList();
tests/CommunityToolkit.Datasync.Client.Test/Helpers/ServiceApplicationFactory.cstests/CommunityToolkit.Datasync.Server.Test/Helpers/ServiceApplicationFactory.cs
Tests that need a deleted movie already call SoftDelete(...) explicitly, so they are unaffected.
A more robust option is to also restore or reset the repository per test, as ResetInMemoryMovies() already does for the offline push tests. That removes the cross-test state sharing entirely, at some cost in test runtime.
Additional context
Delete_* tests that hard-delete a movie remove it from the repository, so they don't cause this problem. Only soft-deleted rows that stay in the repository do.
- Lenguaje dominante
- C#
- Estrellas
- 184
- Forks
- 48
- Merge medio
- 21 min
- PR fusionados (30 d)
- 7
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de CommunityToolkit/Datasync
-
Blocked dependencies Server
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
CommunityToolkit/Datasync#594 ·
-
dependencies Examples
Dificultad 4/5 3-5 días Aptitud para principiantes 40/100
CommunityToolkit/Datasync#593 ·
-
dependencies Infrastructure
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
CommunityToolkit/Datasync#592 ·
-
dependencies Infrastructure
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
CommunityToolkit/Datasync#591 ·
-
dependencies Infrastructure
Dificultad 2/5 1-3 horas Aptitud para principiantes 55/100
CommunityToolkit/Datasync#590 ·
Todos los issues de CommunityToolkit/Datasync
Issues similares
-
t/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
dotnet/maui#39950 · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
NimblePros/deviq-hugo#121 ·
Los mantenedores suelen responder en 1 día
-
RANDOM_REPLACE does not keep the date format when the month abbreviation has a trailing periodAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
philterd/phileas-dotnet#188 ·
-
Add All ContributorsAbiertoenhancement ready-for-human
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
fboucher/2d6-dungeon-app#288 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 80/100
Unity-Technologies/unity-agent-plugin#118 ·
Los mantenedores suelen responder en 1 día