Add tooling to parse test assertion in tests

[KevinFairise2]

What does this PR do?

Motivation

Describe how you validated your changes

Additional Notes

[github-actions]

AI review by Codex (OpenAI) - workflow run

The patch is incorrect: function-value assignments and platform-specific suite declarations can silently lose assertions. These gaps contradict the analyzer’s documented behavior. Validation was limited to source inspection.

[github-actions]

[P2] Preserve callable references when assigning function values

For check := checkTags; check(t, tags) or check := s.checkTags, this creates a variable without fnRefs. resolveCallee then finds the variable and returns its empty references instead of following the helper, silently omitting its assertions. Resolve and store callable references here, including closure aliases, as bindParams already does for function-valued arguments.

[github-actions]

[P2] Expand every platform variant of a suite method

The loader deliberately ignores build constraints and retains multiple declarations of each method, but suite expansion keeps only decls[0]. If a suite defines the same test or hook in Linux and Windows files, assertions from the remaining variants disappear when analyzing its top-level runner. Append all declarations for the selected method name while still suppressing overridden embedded methods.

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor 11cd1667:

Results for datadog-agent_7.86.0~devel.git.314.d5260ba.pipeline.143777463-1_amd64.deb:

No change detected

Results for datadog-iot-agent_7.86.0~devel.git.314.d5260ba.pipeline.143777463-1_amd64.deb:

No change detected

[dd-octo-sts]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 11cd166
📊 Static Quality Gates Dashboard
🔗 SQG Job

33 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64	755.265 MiB
✅	agent_deb_amd64_fips	688.282 MiB
✅	agent_heroku_amd64	319.144 MiB
✅	agent_msi	653.834 MiB
✅	agent_rpm_amd64	755.248 MiB
✅	agent_rpm_amd64_fips	688.266 MiB
✅	agent_rpm_arm64	725.788 MiB
✅	agent_rpm_arm64_fips	664.371 MiB
✅	agent_suse_amd64	755.248 MiB
✅	agent_suse_amd64_fips	688.266 MiB
✅	agent_suse_arm64	725.788 MiB
✅	agent_suse_arm64_fips	664.371 MiB
✅	docker_agent_amd64	811.427 MiB
✅	docker_agent_arm64	806.594 MiB
✅	docker_agent_jmx_amd64	1002.297 MiB
✅	docker_agent_jmx_arm64	986.244 MiB
✅	docker_cws_instrumentation_amd64	7.443 MiB
✅	docker_cws_instrumentation_arm64	6.877 MiB
✅	docker_dogstatsd_amd64	39.547 MiB
✅	docker_dogstatsd_arm64	37.629 MiB
✅	docker_host_profiler_amd64	308.722 MiB
✅	docker_host_profiler_arm64	319.865 MiB
✅	dogstatsd_deb_amd64	30.289 MiB
✅	dogstatsd_deb_arm64	28.278 MiB
✅	dogstatsd_rpm_amd64	30.289 MiB
✅	dogstatsd_suse_amd64	30.289 MiB
✅	iot_agent_deb_amd64	47.371 MiB
✅	iot_agent_deb_arm64	43.837 MiB
✅	iot_agent_deb_armhf	44.652 MiB
✅	iot_agent_rpm_amd64	47.371 MiB
✅	iot_agent_suse_amd64	47.370 MiB
✅	docker_cluster_agent_amd64	211.197 MiB
✅	docker_cluster_agent_arm64	224.162 MiB

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Job ID: 36ee7a74-ef4c-40d8-bde3-d972880c99b7

Baseline: 11cd166
Comparison: d5260ba
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	dsd_uds_client_drop_detector_cpu	% cpu utilization	+0.78	[+0.30, +1.25]	1	Logs
➖	dsd_uds_10mb_3k_timestamped_contexts_cpu	% cpu utilization	+0.56	[+0.32, +0.80]	1	Logs
➖	quality_gate_logs	% cpu utilization	+0.47	[-0.41, +1.35]	1	Logs bounds checks dashboard
➖	python_openmetrics	% cpu utilization	+0.28	[-0.40, +0.96]	1	Logs bounds checks dashboard
➖	quality_gate_security_no_fs_load	memory utilization	+0.16	[+0.08, +0.24]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	+0.02	[-0.02, +0.06]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	-0.08	[-0.11, -0.04]	1	Logs bounds checks dashboard
➖	quality_gate_private_action_runner	memory utilization	-0.11	[-0.23, +0.01]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.31	[-0.39, -0.24]	1	Logs bounds checks dashboard
➖	dsd_uds_10mb_3k_timestamped_contexts_memory	memory utilization	-0.34	[-0.56, -0.12]	1	Logs
➖	quality_gate_security_mean_fs_load	memory utilization	-0.42	[-0.46, -0.38]	1	Logs bounds checks dashboard
➖	quality_gate_metrics_logs	memory utilization	-1.45	[-1.67, -1.22]	1	Logs bounds checks dashboard

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	python_openmetrics	checks_execution_time	10/10	81.53 ≤ 100	bounds checks dashboard
✅	python_openmetrics	cpu_usage	10/10	1344.57 ≤ 1500	bounds checks dashboard
✅	python_openmetrics	memory_usage	10/10	4.33GiB ≤ 4.75GiB	bounds checks dashboard
✅	quality_gate_idle	intake_connections	10/10	4 ≤ 5	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	178.51MiB ≤ 181MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	765.08KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	2 ≤ 5	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	472.73MiB ≤ 542MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	1.14MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	16 ≤ 40	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	212.75MiB ≤ 228MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	264.04MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	396.18 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	19 ≤ 40	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	413.88MiB ≤ 455MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	total_bytes_received	10/10	0.95GiB ≤ 1.04GiB	bounds checks dashboard
✅	quality_gate_private_action_runner	memory_usage	10/10	73.65MiB ≤ 77MiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	30.38 ≤ 100	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	332.41MiB ≤ 357MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	68.30 ≤ 200	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	307.44MiB ≤ 337MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	24.95 ≤ 100	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	313.68MiB ≤ 348MiB	bounds checks dashboard

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_security_idle, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_private_action_runner, bounds check memory_usage: 10/10 replicas passed. Gate passed.