Migrate OpenTelemetry smoke test to JUnit

[PerfectSlayer]

What Does This Do

This PR migrates the OpenTelemetry 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.

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-prod-us1-2]

More details

The JUnit migration preserves the OpenTelemetry smoke application launch and validates its one annotated trace plus ten sequential manual traces with the new backend assertions. No diff-only behavioral regression was confirmed; no additional tests recommended because the existing application shape is deterministic and the attempted module execution was blocked by unavailable Gradle/JDK tooling.

Was this helpful? React 👍 or 👎

_{📊 Validated against 3 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit 9eece4a · 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: 9eece4ad18

ℹ️ 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	13.98 s	13.98 s	[-0.9%; +0.9%] (no difference)
startup:insecure-bank:tracing:Agent	12.82 s	12.95 s	[-1.6%; -0.3%] (maybe better)
startup:petclinic:appsec:Agent	17.50 s	17.28 s	[+0.5%; +2.1%] (maybe worse)
startup:petclinic:iast:Agent	17.40 s	17.53 s	[-1.5%; -0.1%] (maybe better)
startup:petclinic:profiling:Agent	17.38 s	17.34 s	[-0.9%; +1.3%] (no difference)
startup:petclinic:sca:Agent	17.41 s	17.25 s	[+0.0%; +1.7%] (maybe worse)
startup:petclinic:tracing:Agent	16.51 s	16.60 s	[-1.4%; +0.4%] (no difference)

Commit: 5b007a3e · 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.

[datadog-datadog-prod-us1-2]

View session in Datadog

Bits Code status: ✅ Done

Comment @DataDog to request changes

[bric3]

Looks good to me, however I think the comment on assertTrace and the list of spans deserves some attention.

[datadog-datadog-prod-us1-2]

More details

The JUnit test keeps the prior check for 11 traces and exit value 0. It also checks each trace and span with the new smoke test framework.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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

[datadog-datadog-prod-us1-2]

More details

The JUnit migration preserves the 11 expected OpenTelemetry traces and the zero exit code check. The shared smoke-test framework has no reportable static correctness issue.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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

[PerfectSlayer]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-24 08:52:27 UTC ℹ️ Start processing command /merge

---

2026-08-24 08:52:31 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-08-24 09:19:51 UTC ❌ MergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for cb8d3b1:

• test_ssi_smoke: [ibm8, 6/8]

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

[datadog-datadog-prod-us1-2]

The new span-link check accepts any three hexadecimal span IDs. Broken links can pass without pointing to the shard spans.

_{Open Bits AI session}

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

[AlexeyKuznetsov-DD]

LGTM, left couple of generic questions.

[PerfectSlayer]

I really don’t like aggressively closing discussion to proceed with merge… That feels so rude.
This is a stacked PR, I expect follow up changes and polish to be added to the stack.

[PerfectSlayer]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-25 07:23:51 UTC ℹ️ Start processing command /merge

---

2026-08-25 07:23:55 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-08-25 08:20:05 UTC ℹ️ MergeQueue: This merge request was merged