Migrate dd-trace-core groovy files to java part 14

[jpbempel]

What Does This Do

we migrate 3 tests from traceAgentTest module

Motivation

this is part of the effort to migrate groovy tests to Java/JUnit
part1: #11053
part2: #11062
part3: #11085
part4: #11146
part5: #11217
part6: #11362
part7: #11374
part8: #11437
part9: #11488
part10: #11543
part11: #11566
part12: #11619
part13: #12253

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: [PROJ-IDENT]

[dd-octo-sts]

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

• Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 41dae6b7d8

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[datadog-datadog-prod-us1]

After DDApiIntegrationTest runs locally, JUnit does not run the parent container cleanup. The Docker agent stays active.

_{Open Bits AI session}

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

[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.88 s	14.71 s	[+0.3%; +2.1%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.58 s	13.70 s	[-1.6%; -0.0%] (maybe better)
startup:petclinic:appsec:Agent	16.97 s	16.76 s	[+0.5%; +2.0%] (maybe worse)
startup:petclinic:iast:Agent	16.93 s	16.47 s	[-1.7%; +7.2%] (no difference)
startup:petclinic:profiling:Agent	16.67 s	16.83 s	[-2.1%; +0.2%] (no difference)
startup:petclinic:sca:Agent	16.76 s	16.60 s	[+0.1%; +1.8%] (maybe worse)
startup:petclinic:tracing:Agent	16.10 s	16.04 s	[-0.6%; +1.3%] (no difference)

Commit: 14678560 · 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]

I spot a few things.

[datadog-datadog-prod-us1]

More details

The Java tests keep the same setup, input cases, checks, and helper behavior as the removed Groovy tests. The support changes only make report() available to tests and set the required format order.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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

[bric3]

I'm not sure about the tabletest/google format change. But let's approve and we can revert that change specifically if there's an issue.

I'm OK with spotless off as well.