Fix: Filter forced discovery plan to test location

[anmarchenko]

What

Filter full-discovery planner results through the resolved test file selection before writing runnable plan artifacts. This keeps .testoptimization/runner/test-files.txt and tests-split/runner-* scoped to DD_TEST_OPTIMIZATION_RUNNER_TESTS_LOCATION, even when DD_TEST_OPTIMIZATION_RUNNER_FORCE_FULL_TEST_DISCOVERY=true makes discovery observe tests outside that location.

Why

Forced full discovery can intentionally scan broadly enough to classify suite-level skips, but the runnable plan artifacts are consumed by CI jobs that are configured for a specific test glob. If full-discovery-only files outside that glob leak into the plan, downstream shards can try to run files from another module or suite and fail to load them.

E2E testing

Run planning with suite-level skipping, forced full discovery, and a narrow test location glob. The regression test covers a runnable file inside the glob, a fully skipped file inside the glob, and a runnable file outside the glob. The expected plan contains only the runnable in-glob file in runner/test-files.txt and all runner/tests-split/runner-* files.

[datadog-datadog-us1-prod]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 89.55%
• Overall Coverage: 88.12% (-0.05%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 0a6df2b | Docs | Datadog PR Page | Give us feedback!}

[datadog-datadog-us1-prod]

More details

PR correctly filters forced full discovery results through the resolved test location pattern before writing plan artifacts. All tests pass, including a comprehensive regression test validating the three critical scenarios: in-location runnable files are included, in-location skipped files are excluded from the plan, and out-of-location files are excluded. No behavioral regressions or edge-case failures detected.

Was this helpful? React 👍 or 👎

_{📊 Validated against 15 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit 0a6df2b · What is Autotest? · Any feedback? Reach out in #autotest}