Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

JUnit and request recorders both record the same integration test; no way to pick one

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

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
28/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
java, spring-boot
Domínio
testing, tooling

Direção de pesquisa

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.

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

Descrição

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.

Written by Devin

Linguagem predominante
Java
Estrelas
88
Forks
17
Merge médio
2d 2h
PRs com merge (30d)
1

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 getappmap/appmap-java

Todas as issues de getappmap/appmap-java

Issues semelhantes

Mais issues de Java

Receba novas issues na sua caixa de entrada

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