Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Test HTTP command error responses through real endpoints

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

Los mantenedores suelen responder en 7 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
58/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp
Área
api, testing

Línea de trabajo

Start with ResultExtensions.cs and the existing ASP.NET Core test application; trace the separate minimal-API and controller command mappings. Add hosted HTTP tests for each listed command outcome, then run the affected endpoint tests and collect focused coverage. Done means both mappings assert status, response body, and problem-details content type without checking full stack traces.

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

Descripción

Problem

The HTTP result-mapping code has approximately 24% line coverage in the October 5, 2026 .NET 10 coverage run. Most error-response paths are untested. These paths define the status codes and problem-details bodies that API clients rely on. You can view a test coverage report I generated here: index.html

Source: ResultExtensions.cs.

Proposed tests

Send HTTP requests to test endpoints backed by command services that produce each outcome:

Command outcome Expected response
Success HTTP 200 with the expected result body
Domain validation failure HTTP 400 with domain validation details
Missing aggregate HTTP 404 with problem details
Optimistic concurrency conflict HTTP 409 with problem details
Unexpected failure HTTP 500 with problem details

Cover both minimal-API and controller command mappings, since they use separate result-conversion paths. Assert the response content type and stable problem-details fields, including domain errors where applicable.

Acceptance criteria

  • Each outcome is exercised through an HTTP request to a hosted test application.
  • Both minimal-API and controller mappings are covered.
  • Assertions verify status codes and response bodies, rather than only whether requests complete.
  • Error responses use the expected problem-details content type and structure.
  • Tests avoid brittle comparisons of full exception stack traces.
  • No direct tests of ResultExtensions, external database, or Docker container are required.

Validation

Extend the existing ASP.NET Core test application and run the affected endpoint tests. Collect focused coverage for the HTTP result-mapping paths; do not rerun unrelated provider suites.

Lenguaje dominante
C#
Estrellas
512
Forks
99
Merge medio
5 d 6 h
PR fusionados (30 d)
5

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 Eventuous/eventuous

Todos los issues de Eventuous/eventuous

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.