Add muzzle test source files

[sarahchen6]

What Does This Do

Add test source files for Muzzle tests for CI/CD Optimization reporting reasons

Motivation

Currently Muzzle tests are listed with UNKNOWN as their test source file in CI/CD Optimization (example). Instead, assign their proper source file so that related dependent metrics such as codeowners are correct as well.

Additional Notes

We can see the results in CI Optimization here:

• SHA without working test source files: https://app.datadoghq.com/ci/ci-cd/explorer?query=test_level%3Atest%20%40git.repository.id_v2%3Agithub.com%2Fdatadog%2Fdd-trace-java%20%40git.branch%3Asarahchen6%2Fadd-muzzle-test-sourcefiles%20%40git.commit.sha%3Af6f49b2b7d11239ccc16fede27d774069fc96dd8%20%40test.name%3Amuzzle%2A&agg_m=count&agg_m_source=base&agg_t=count&ci_cd_explorer_tab=tests&citest_explorer_sort=%40test.source.file%2Casc&cols=%40test.status%2Ctimestamp%2C%40test.suite%2C%40test.name%2C%40duration%2C%40test.service%2C%40git.branch%2C%40test.codeowners%2C%40test.source.file&currentTab=overview&eventStack=&fromUser=false&refresh_mode=sliding&start=1787246271997&end=1787332671997&paused=false
• SHA with working test source files: https://app.datadoghq.com/ci/ci-cd/explorer?query=test_level%3Atest%20%40git.repository.id_v2%3Agithub.com%2Fdatadog%2Fdd-trace-java%20%40git.branch%3Asarahchen6%2Fadd-muzzle-test-sourcefiles%20%40git.commit.sha%3Acd2d2cc0d000126f4412dd5ae71356e5fc06b376%20%40test.name%3Amuzzle%2A&agg_m=count&agg_m_source=base&agg_t=count&ci_cd_explorer_tab=tests&citest_explorer_sort=%40test.source.file%2Casc&cols=%40test.status%2Ctimestamp%2C%40test.suite%2C%40test.name%2C%40duration%2C%40test.service%2C%40git.branch%2C%40test.codeowners%2C%40test.source.file&currentTab=overview&eventStack=&fromUser=false&refresh_mode=sliding&start=1787252005430&end=1787338405430&paused=false

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]

[datadog-prod-us1-5]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 58.61% (-0.05%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: cd2d2cc | Docs | View more details | Give us 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.00 s	13.98 s	[-0.5%; +0.7%] (no difference)
startup:insecure-bank:tracing:Agent	12.91 s	12.97 s	[-1.2%; +0.2%] (no difference)
startup:petclinic:appsec:Agent	17.57 s	17.24 s	[+1.1%; +2.8%] (significantly worse)
startup:petclinic:iast:Agent	17.50 s	17.54 s	[-0.9%; +0.4%] (no difference)
startup:petclinic:profiling:Agent	17.43 s	17.24 s	[+0.1%; +2.1%] (maybe worse)
startup:petclinic:sca:Agent	17.45 s	17.35 s	[-0.3%; +1.5%] (no difference)
startup:petclinic:tracing:Agent	16.58 s	16.82 s	[-2.5%; -0.3%] (maybe better)

Commit: cd2d2cc0 · 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-prod-us1-5]

More details

The change keeps the Muzzle source path in each collected test case. The static review finds no reportable defect.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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

[AlexeyKuznetsov-DD]

Looks good to me, but I think it is worth to get @bric3 approval, since he refactored Muzzle heavily