Add Android/Robolectric visibility to Test Optimization spans

[daniel-mohedano]

What Does This Do

• Implements additional visibility to test spans for test emulated with the Android SDK through Robolectric. These tests are already traced OOTB as JUnit4 tests.
  • New per-test span tags:
    • test.android.api_level
    • test.android.release
    • test.android.codename
    • test.android.robolectric.version
  • New is_android boolean field on the test_event_finished telemetry metric.
• Adds a new GradleDaemonSmokeTest test to validate the new instrumentation and tagging. It covers both @RunWith(RobolectricTestRunner.class) and @RunWith(AndroidJUnit4.class).

Motivation

With Android tests already being supported OOTB, these changes provide better visibility for customers using the Robolectric framework.

Additional Notes

test-environment-trigger: skip

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
• Add your completed PR to the merge queue by commenting /merge. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
  • Get more information in this doc

Jira ticket: SDTEST-3887 [SDTEST-3888] [SDTEST-3889]

[datadog-datadog-us1-prod]

🎯 Code Coverage (details)
• Patch Coverage: 55.56%
• Overall Coverage: 56.91% (-0.03%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 8d8b6d2 | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

🟡 Java Benchmark SLOs — Performance SLO warning (near threshold)

Suite	Status
Startup	🟡 warning

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.96 s	[-0.5%; +1.1%] (no difference)
startup:insecure-bank:tracing:Agent	12.95 s	12.95 s	[-0.7%; +0.7%] (no difference)
startup:petclinic:appsec:Agent	16.95 s	16.50 s	[+1.8%; +3.6%] (significantly worse)
startup:petclinic:iast:Agent	16.98 s	17.04 s	[-1.3%; +0.6%] (no difference)
startup:petclinic:profiling:Agent	16.82 s	17.01 s	[-2.3%; +0.1%] (no difference)
startup:petclinic:sca:Agent	16.96 s	16.68 s	[+0.5%; +2.9%] (maybe worse)
startup:petclinic:tracing:Agent	16.03 s	16.02 s	[-0.7%; +0.9%] (no difference)

Commit: 8d8b6d27 · 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.