Test HTTP command error responses through real endpoints
维护者通常 7 天内回复
还没有人认领这个 Issue。
评估
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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.
- 主要语言
- C#
- 星标
- 512
- 派生
- 99
- 平均合并
- 5 天 6 小时
- 30 天内合并 PR
- 5
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Eventuous/eventuous 的其他 Issue
-
MongoDB integration tests fail on newer GitHub Actions runner kernels可能已有人在做 @nmummau 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 74/100
Eventuous/eventuous#626 · 2 条评论 ·
维护者通常 7 天内回复
-
`dotnet format style --verify-no-changes` fails with naming violations and unnecessary imports可能已有人在做 @nmummau 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 80/100
Eventuous/eventuous#624 · 1 条评论 ·
维护者通常 7 天内回复
-
难度 5/5 一周以上 新手友好度 35/100
Eventuous/eventuous#627 · 1 条评论 ·
维护者通常 7 天内回复
-
SQL Server: `append_events` does not need the `@inserted` table variable可能已有人在做 @nmummau 于 7 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 20/100
Eventuous/eventuous#619 · 1 条评论 ·
维护者通常 7 天内回复
-
SQL Server: stream reads do one key lookup per event, and `IDX_EventsStream` duplicates `UQ_StreamIdAndStreamPosition`可能已有人在做 @nmummau 于 7 天前认领。 未关闭
难度 3/5 1-2 天 新手友好度 18/100
Eventuous/eventuous#618 · 1 条评论 ·
维护者通常 7 天内回复
查看 Eventuous/eventuous 的全部 Issue
相似的 Issue
-
[BUG]: Position intent set on a simple order is dropped when it becomes a bracket, OCO or OTO order可能已有人在做 @RaphaelFakhri 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 78/100
alpacahq/alpaca-trade-api-csharp#903 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 64/100
joinrpg/joinrpg-net#5752 ·
维护者通常 1 天内回复
-
bug ux
难度 2/5 1-3 小时 新手友好度 78/100
CodeForFire/lagebuch#714 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
dimitar-radenkov/Pointframe#294 ·
维护者通常 1 天内回复
-
kind/feature-request
难度 2/5 1-3 小时 新手友好度 68/100
Altinn/altinn-correspondence#2154 ·
维护者通常 1 天内回复