Comprehensive aggregation REST tests

[polyfractal]

There are only a few REST tests that verify the body of aggregation results. We should have a more comprehensive suite of tests that check the body under a variety of conditions and options.

Metrics:

• Avg Aggregation (Add REST tests for avg/min/max/sum metric aggs #26225)
• Boxplot Aggregation (Adds some REST tests for boxplot metric aggregations. #78354)
• Cardinality Aggregation (Add REST tests for value_count, stats, extended_stats and cardinality aggs #26239)
• Extended Stats Aggregation (Add REST tests for value_count, stats, extended_stats and cardinality aggs #26239)
• Geo Bounds Aggregation (More REST tests for geo_bounds aggregation #94742)
• Geo Centroid Aggregation (Enhanced REST tests for geo and cartesian centroid #94964)
• Geo_line Aggregation (Fix bug 94733 geo_line not respecting sort_order #94734)
• Matrix stats
• Max Aggregation (Add REST tests for avg/min/max/sum metric aggs #26225)
• Median absolute deviation (missing compression, I think)
• Min Aggregation (Add REST tests for avg/min/max/sum metric aggs #26225)
• Percentiles Aggregation (Add REST tests for percentiles agg #26266)
• Percentile Ranks Aggregation (Add integration test for percentile_ranks #77815)
• Rate (Add more tests for rate aggregation #95576 )
• Scripted Metric Aggregation (Add REST tests for scripted metric aggregation #95632)
• Stats Aggregation (Add REST tests for value_count, stats, extended_stats and cardinality aggs #26239)
• String stats
• Sum Aggregation (Add REST tests for avg/min/max/sum metric aggs #26225)
• t-test
• Top hits Aggregation (REST tests for top_hits #83690)
• Top metrics
• Value Count Aggregation (Add REST tests for value_count, stats, extended_stats and cardinality aggs #26239)
• Weighted average (Add YAML REST test for the weighted average aggregation #81306))

Bucketing

• Adjacency Matrix Aggregation (Test: assert adjacency matrix cache #69440)
• Auto-interval histogram (REST tests for variable width historam #84836)
• Children Aggregation (A few more tests for parent and child aggs #78264)
• Composite (Rest tests for Composite Histogarm #94753)
• Date Histogram Aggregation
• Date Range Aggregation (Yaml tests for range family aggregations #75434)
• Diversified Sampler Aggregation (Integration tests for diversified sampler #77810)
• Filter Aggregation (Add integration tests for filters #69439)
• Filters Aggregation (Add YAML REST tests for filters bucket agg #27128)
• Geo Distance Aggregation (Craig) - cancelled in favour of ES|QL features
• GeoHash grid Aggregation on geo_point (add basic REST test for geohash_grid #37996) (Expand tests for geo_grid aggregations #94747)
• GeoTile grid Aggregation on geo_point (geotile_grid implementation #37842) (Expand tests for geo_grid aggregations #94747)
• GeoHex grid Aggregation on geo_point (New GeoHexGrid aggregation #82924)
• GeoHash grid Aggregation on geo_shape (Expand tests for geo_grid aggregations #94747)
• GeoTile grid Aggregation on geo_shape (Expand tests for geo_grid aggregations #94747)
• GeoHex grid Aggregation on geo_shape (Expand tests for geo_grid aggregations #94747)
• Global Aggregation (Fix profiled global agg #71575)
• Histogram Aggregation (Add REST tests for histogram aggregation #72322)
• IP Range Aggregation (Yaml tests for range family aggregations #75434)
• Missing Aggregation (add tests for missing aggregation #53214)
• Multi-terms (only basics are tested) (More yaml tests for multi_terms aggregation #94975)
• Nested Aggregation (Tests for running composite under nested aggregation #68243)
• Parent (A few more tests for parent and child aggs #78264)
• Range Aggregation (expanded in Yaml tests for range family aggregations #75434)
• Rare terms (added when the agg was added in Add RareTerms aggregation #35718)
• Reverse nested Aggregation (Add a REST layer test for reverse_nested #83874)
• Sampler Aggregation (Integration test for sample aggragator #77807)
• Significant Terms Aggregation (more minimal than terms but the agg sees less use)
• Significant Text (More debugging info for significant_text #72727)
• Terms Aggregation

Pipeline

• Avg Bucket Aggregation REST tests for avg/max/min/sum_bucket aggs #87009 More REST tests for avg/max/min/sum_bucket aggs #88027
• Bucket Script Aggregation REST tests for bucket_script agg #94749 (Nik)
• Bucket Selector Aggregation Move bucket_selector agg to the agg module #91355
• Bucket sort Enhance REST tests for bucket_sort #91221
• Cumulative cardinality REST tests for cumulative pipeline aggs #88966
• Cumulatve sum REST tests for cumulative pipeline aggs #88966
• Derivative Aggregation Move derivative agg to module #91014
• Max Bucket Aggregation REST tests for avg/max/min/sum_bucket aggs #87009 More REST tests for avg/max/min/sum_bucket aggs #88027
• Min Bucket Aggregation REST tests for avg/max/min/sum_bucket aggs #87009 More REST tests for avg/max/min/sum_bucket aggs #88027
• Moving Function Aggregation REST tests for moving_fn agg #90012
• Moving percentiles Enhance REST tests for moving_percentiles #90569
• Normalize (REST tests for normalize agg #89629)
• Percentiles Bucket Aggregation REST tests for percentiles_bucket agg #88029
• Serial Differencing Aggregation Allow serial_diff under min_doc_count aggs #86401
• Stats Bucket Aggregation REST tests for stats_bucket aggs #87006
• Sum Bucket Aggregation REST tests for avg/max/min/sum_bucket aggs #87009 More REST tests for avg/max/min/sum_bucket aggs #88027

[javanna]

Question: do we want to have these as yaml tests so the language clients can run them too? Or shall we consider making them java tests that se the low-level REST client instead?

[polyfractal]

I was targeting the yaml tests so that clients could also run them, figured that would provide the widest benefit to new tests (since basically none of the clients do any body testing at all, it may smoke out some issues). And yaml tests are sometimes easier to write :)

But I could be convinced either way. What do you think?

[javanna]

I am fine with moving forward with yaml tests, I don't have a strong opinion, I just wanted to make sure that we consider writing java tests too.

[markharwood]

cc @elastic/es-search-aggs

[not-napoleon]

The numbering is fairly arbitrary. Feel free to just pick the next available multiple of ten and start there. I believe there are historical reasons for it, but at this point it's mostly tradition. Thanks for helping out!

[nik9000]

I believe there are historical reasons for it, but at this point it's mostly tradition.

Reminds me of writing basic in middle school.

[not-napoleon]

Reminds me of writing basic in middle school.

I can't tell if that's a point in favor of or against continuing the practice.

[elasticsearchmachine]

Pinging @elastic/es-analytics-geo (Team:Analytics)

[elasticsearchmachine]

Pinging @elastic/es-analytical-engine (Team:Analytics)