[SDTEST-3826] Extend plan reporting#76
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f149496587
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
E2E Test Report: SUCCESSTested by: Shepherd Agent (autonomous QA for Datadog Test Optimization) Test Environment
Results
Issues FoundNone. Observed expected Forem planning warnings because TIA/test skipping were disabled by the mockdog scenario, so full discovery was cancelled and ddtest used fast file discovery. The fallback discovered all 23 policy spec files, and mocked suite durations were fetched successfully. Verification
Test Methodology
Full ddtest Report OutputThis E2E test was performed by Shepherd - autonomous QA agent for Datadog Test Optimization. |
What
Extend the DDTest plan report with richer planning diagnostics:
Why
The plan report is the best place for users to understand why a run was split the way it was. Keeping these details in the report makes the output easier to scan and avoids duplicating the same information in logs. The slowest-suite reporting uses bounded top-N collection so it stays small even for large repositories.
E2E testing
Run
ddtest planon a repository with report output enabled and verify the report includes DDTest settings, Datadog settings, planning/split details, slow suites on dedicated runners when applicable, and the 10 slowest test suites overall.Appendix
Example golden report from
internal/planner/report_test.go: