JUnit and request recorders both record the same integration test; no way to pick one
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 28/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- java, spring-boot
研究方向
Start by reproducing with mvn -Dtest=PetClinicIntegrationTests#testOwnerDetails test in spring-petclinic, then compare the outputs under tmp/appmap/junit and tmp/appmap/request_recording. The issue leaves open whether the fix is a configuration switch or a documented rule, so a maintainer decision is needed first. Done means one recorder is chosen when both would fire, with the rule or setting documented.
由索引模型根據 Issue 內容生成。
描述
Summary
A single Spring Boot integration test that issues an HTTP request through a real port produces two recordings of the same behavior: one from the JUnit recorder, one from the request recorder. Both recorders are on by default, neither knows about the other, and there is no documented setting to disable one.
Agent 1.30.1, spring-petclinic @ b26f235.
Repro
mvn -Dtest=PetClinicIntegrationTests#testOwnerDetails test
ls tmp/appmap/junit tmp/appmap/request_recording
Observed
tmp/appmap/junit/org_..._PetClinicIntegrationTests_testOwnerDetails.appmap.json
tmp/appmap/request_recording/1789755390_129__owners_1.appmap.json
The JUnit recording contains the test method and everything under it; the request one contains the request, controller and SQL. They overlap almost entirely. The request recording's filename embeds a timestamp and a port-dependent counter, so it differs on every run and cannot serve as a stable baseline identity (the gold-traces engine's discover returns both and leaves the choice open).
Expected
A setting to select which recorder runs when both would fire (e.g. suppress request recordings that occur inside an active JUnit recording), or at least document the rule: curate the JUnit recording, use a request recording only when no test drives the endpoint.
- 主要語言
- Java
- 星號
- 88
- 分支
- 17
- 平均合併
- 2 天 2 小時
- 30 天內合併 PR
- 1
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
getappmap/appmap-java 的其他 Issue
-
appmap.yml packages path matching zero classes yields a healthy-looking recording with no warning未關閉
難度 3/5 1-2 天 新手友好度 45/100
getappmap/appmap-java#332 · 1 則留言 ·
-
Git metadata dropped in a git worktree (.git file with gitdir: pointer not followed)可能已有人在做 @dividedmind 於 1 天前認領。 未關閉
getappmap/appmap-java#331 · 1 則留言 · 已指派 1 人 ·
-
Labeled methods should always be recorded, even if they match trivial-method filters可能已有人在做 @kgilpin 於 191 天前認領。 未關閉
getappmap/appmap-java#323 · 1 個 reaction · 已指派 2 人 ·
-
難度 3/5 1-2 天 新手友好度 35/100
getappmap/appmap-java#322 ·
-
難度 5/5 一週以上 新手友好度 35/100
getappmap/appmap-java#308 ·
查看 getappmap/appmap-java 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
sqlcipher/sqlcipher-android#97 · 1 則留言 ·
-
bug IIIF interoperability
難度 2/5 1-3 小時 新手友好度 72/100
-
難度 2/5 1-3 小時 新手友好度 72/100
-
難度 2/5 1-3 小時 新手友好度 68/100
Netcracker/qubership-integration-platform#1046 ·
維護者通常 2 天內回覆