Cleanups for nested test_suite or java_test under trim_test_configuration For test_suite, no longer make TestConfiguration a hard requirement (similar to https://github.com/bazelbuild/bazel/commit/215a0f70c81a7574d5d9fe5f771446aaf622f21e). Also, split out the older 'temporary hack' of TestTags in TestProvider (used in test_suite filtering) to its own provider, TestTagsProvider, that is now always provided by tests. For java_test, change [Bazel]JavaSemantics to more gracefully handle a missing TestConfiguration. For persistent test runner related functions, returns false when missing the TestConfiguration (as it is assumed to be irrelevant). For legacy java_test matters, assumes test_arg is empty (as again assumed to be irrelevant). RELNOTES: NONE PiperOrigin-RevId: 334547057
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
See CONTRIBUTING.md
