Add documentation and tests for `cc_test` implicit output targets #18018 implies that the implicit output targets added by the `cc_binary` rule (documented [here](https://bazel.build/reference/be/c-cpp#cc_binary_implicit_outputs)) are not mirrored by the `cc_test` rule. However, it appears that Bazel 6.0 does in fact have the implicit output targets of the `cc_binary` rule mirrored by the `cc_test` rule. Given that Bazel 6.0 already seems to have the implicit output targets mirrored by the `cc_test` rule, I figured that no source code changes are required for Bazel 6.0. However, I couldn't find documentation for this feature, and I couldn't find tests either. I did the following: - I added documentation for the implicit output targets under the `cc_test` rule. - I added unit tests for the implicit output targets under the `cc_test` rule. - I added integration tests for the implicit output targets under the `cc_test` rule. Closes #18275. PiperOrigin-RevId: 530248329 Change-Id: I46756464d29b6840c92df704a43f63c3030b71dc
{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:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
