Migrate Spring Boot RabbitMQ smoke test to JUnit

[PerfectSlayer]

What Does This Do

This PR migrates the Spring Boot RabbitMQ smoke tests to the new JUnit smoke test framework.

Motivation

The new tests checks the whole trace structures and span values, in addition to trace payload validity and invariants.
It also check that three round-trips are present (no only one) and the trace is fully-connected.

Additional Notes

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: APMLP-1247

[datadog-datadog-us1-prod]

The migrated test changes RabbitMQ's known teardown-error allowlist from the actual client text occured to occurred. When either app is stopped, that disconnect log is treated as an unexpected error and the smoke test fails in teardown; restore the original spelling.

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 1201890 · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1201890609

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.81 s	14.69 s	[+0.0%; +1.6%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.52 s	13.72 s	[-2.3%; -0.6%] (maybe better)
startup:petclinic:appsec:Agent	17.53 s	17.39 s	[-0.2%; +1.8%] (no difference)
startup:petclinic:iast:Agent	17.44 s	16.88 s	[-1.1%; +7.7%] (no difference)
startup:petclinic:profiling:Agent	17.48 s	17.42 s	[-0.9%; +1.6%] (no difference)
startup:petclinic:sca:Agent	17.48 s	17.37 s	[-0.3%; +1.7%] (no difference)
startup:petclinic:tracing:Agent	16.66 s	16.51 s	[+0.1%; +1.7%] (maybe worse)

Commit: 8f3685a7 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[bric3]

LGTM, a few tidbits though.

[datadog-datadog-us1-prod]

The new 12-span matcher cannot match the three trace chunks that the two JVMs send for each round trip. The smoke test waits for 60 seconds and then fails.

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 8f3685a · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[mhdatie]

Few remarks but straightforward otherwise 👍

[PerfectSlayer]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-25 08:50:26 UTC ℹ️ Start processing command /merge

---

2026-08-25 08:50:31 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-08-25 09:39:51 UTC ℹ️ MergeQueue: This merge request was merged