Fix tests

[lwr20]

No description provided.

[Copilot]

Pull Request Overview

Updates the Elasticsearch document tests to use the new stats.ResultSummary type and reflect added DNSPerf config fields.

• Replace map[int]float64 with stats.ResultSummary for timing metrics
• Extend expected JSON to include new RunStress, TestDNSPolicy, NumTargetPods, and TargetType fields
• Change empty summaries from null to {} in blank test

Comments suppressed due to low confidence (3)

pkg/elasticsearch/elasticsearch_test.go:71

• [nitpick] The JSON keys for stats (e.g., min, max, avg, P50, P75, P90, P99, datapoints) mix casing conventions. Consider adopting a consistent naming style (all lowercase or camelCase) for clarity.

"dnsperf":{"LookupTime":{"min":0.001,"max":0.013641,"avg":0.004745,"P50":0.00364,"P75":0.004745,"P90":0.006914,"P99":0.013641,"datapoints":17}

pkg/elasticsearch/elasticsearch_test.go:71

• [nitpick] The test uses a large inline JSON string, which can be brittle and hard to maintain. Consider constructing the expected document programmatically or using a golden file to make updates easier.

expectedDoc := `{"config":...`

pkg/elasticsearch/elasticsearch_test.go:87

• The output shape for empty summaries changed from null to {}. This is a breaking API change for consumers; verify it’s intentional and update any downstream mappings or documentation accordingly.

"dnsperf":{"LookupTime":{},"ConnectTime":{},"DuplicateSYN":0