[SDTEST-3870] Improve planner report narrative#100
Conversation
There was a problem hiding this comment.
More details
Report generation refactoring is correct and handles all input variations properly. The PR separates backend inventory from planner decisions, tracks applied skippables accurately across multiple match types (TIA test, TIA suite, disabled test), and correctly formats output based on discovery mode. Reflection-based settings comparison produces only non-default values. All 30+ test scenarios pass including edge cases (zero values, unavailable data, malformed input, singular/plural formatting). No regressions detected.
📊 Validated against 32 scenarios · Open Bits AI session
🤖 Datadog Autotest · Commit ab3a902 · What is Autotest? · Any feedback? Reach out in #autotest
🎉 All green!🧪 All tests passed 🎯 Code Coverage (details) 🔗 Commit SHA: a95edf6 | Docs | Datadog PR Page | Give us feedback! |
E2E Test Report: SUCCESSTested by: Shepherd Agent (autonomous QA for Datadog Test Optimization) Test Environment
Results
Issues FoundNo product issues found. One environment note: the real EU backend validation required explicit approval because it sends repository/test metadata to VerificationThe real backend validation was performed through Datadog EU API responses used by Test Methodology
Real EU Backend DDTest Plan ReportThis E2E test was performed by Shepherd - autonomous QA agent for Datadog Test Optimization. |
What
Reworks the DDTest plan report and simplifies the report data flow:
Planningfocused on planner decisions: discovery, duration application, applied skips, run set size, and split quality.testsorsuites, matching the configured skipping level.Why
The previous planner report mixed backend inventory, planner actions, and split details in a way that was hard for customers to interpret. It also made the planner and test optimization client carry report-only state, which made the implementation harder to review and maintain.
This keeps the customer report concise while reducing the amount of plumbing outside
report.goandreport_data.go.E2E testing
Manual scenario: run
ddtest planwith report output enabled on a suite-skipping project that has backend known tests, skippables, managed flaky tests, suite durations, and a configured discovery cache.To test different report shapes, use mock backend.
Test also with real backend (EU target) to confirm that numbers are real.
Confirm the report separates backend-returned data from planning decisions and prints concise labels like this: