testing-internals

Bazel test discovery in tests.cmd works by invoking Bazel targets, discovering tests, and routing them to JUnit 5 and Vintage runners. The execution flow involves bucketing, classpath assembly, and post-discovery filtering to orchestrate test execution.

JUnit 5 test discovery for legacy tests requires the Vintage runner engine to route older JUnit tests correctly. If configuration properties like patterns or groups are misconfigured, post-discovery filtering may exclude legacy tests from the execution bucket.

Debugging test discovery bottlenecks in Bazel involves tracing execution paths from tests.cmd through Bazel targets to the test runners. You can identify bottlenecks by analyzing bucketing, classpath assembly, and post-discovery filtering stages.

The execution flow from tests.cmd to JUnit runners starts with tests.cmd invoking Bazel targets, discovering tests, and routing them to JUnit 5 and legacy JUnit runners. It includes classpath assembly and post-discovery filtering to validate configuration properties.

Yes, tests.cmd supports configuring test bucketing, patterns, and groups. Validating these configuration properties is essential for diagnosing test discovery failures and ensuring tests are correctly routed to the appropriate JUnit runners.

Bazel test targets may not be discovered if tests.cmd encounters configuration issues in patterns or groups during the execution flow. Troubleshooting involves checking post-discovery filtering and classpath assembly to identify where the discovery process fails.