Migrate dynamic config smoke tests to JUnit

[PerfectSlayer]

What Does This Do

This PR migrates the dynamic config smoke tests to the new JUnit smoke test framework.

Motivation

The new tests checks the RC messages (payload and behavior) against the CI test agent, and no longer our own implementation, to avoid validating our implementation by ourselves.

Additional Notes

The CI test agent runs as side car in CI. It will be run using testcontainers on local environment.

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: eaee938397

ℹ️ 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.06 s	13.95 s	[-0.1%; +1.7%] (no difference)
startup:insecure-bank:tracing:Agent	12.91 s	13.00 s	[-1.4%; +0.0%] (no difference)
startup:petclinic:appsec:Agent	16.98 s	16.88 s	[-0.5%; +1.6%] (no difference)
startup:petclinic:iast:Agent	16.97 s	17.08 s	[-1.4%; +0.2%] (no difference)
startup:petclinic:profiling:Agent	16.88 s	16.97 s	[-1.6%; +0.6%] (no difference)
startup:petclinic:sca:Agent	16.82 s	16.82 s	[-1.0%; +0.9%] (no difference)
startup:petclinic:tracing:Agent	16.21 s	16.18 s	[-0.8%; +1.2%] (no difference)

Commit: 186a713a · 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-official]

More details

The JUnit migration preserves the prior RC assertions and compiles cleanly; shared smoke/backend tests also pass. The two changed smoke tests could not execute their child JVMs here because Docker is unavailable for TestAgentBackend, so end-to-end app behavior remains to be confirmed in CI.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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

[datadog-official]

View session in Datadog

Bits Code status: ✅ Done

Comment @DataDog to request changes

[sarahchen6]

Looks like the PR description needs an update, but otherwise LGTM!

[datadog-official]

More details

The JUnit migrations preserve the prior Remote Config behavior. The new tests also use the smoke-test backend lifecycle correctly.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 4ce14fb · 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-25 12:29:00 UTC ℹ️ Start processing command /merge

---

2026-08-25 12:29:10 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-08-25 13:16:35 UTC ℹ️ MergeQueue: This merge request was merged