Refactor Test Optimization API transport#87
Conversation
E2E Test Report: SUCCESSTested by: Shepherd Agent (autonomous QA for Datadog Test Optimization) Test Environment
Results
Primary Run Summary
Issues FoundNo PR-blocking issues found. I also ran Sidekiq to exercise positive TIA skipping. The first Sidekiq attempt failed because Redis was not running locally. After starting Redis, the backend transport and skipping behavior worked, but the Sidekiq test command still failed due playground/environment test failures unrelated to this transport refactor. I used the clean Vagrant pass as the primary E2E result and the Sidekiq run only as additional evidence that the skippable-tests path can drive actual skips. VerificationVerified against the real EU Datadog backend through API/intake responses and debug telemetry. Manual Datadog UI inspection was not performed in this run. Test Methodology
This E2E test was performed by Shepherd - autonomous QA agent for Datadog Test Optimization. |
What
Remove the unused impacted-tests and related copied CI Visibility code, move the Test Optimization API transport under
internal/testoptimization/api, integrate durations into that transport layer, and add focused coverage for the Test Optimization package.Why
This reduces copied dead code from dd-trace-go, makes the Test Optimization API surface easier to reason about, and locks in behavior with tests before the next refactoring step.
E2E testing
Run the full ddtest run with real Datadog backend in a feature branch with local commits. Make sure that git upload and tests skipping works.