| commit | d6ad383a269cac720bfd1a76af87dd312b9313a7 | [log] [tgz] |
|---|---|---|
| author | Googler <hvd@google.com> | Tue Mar 21 09:15:04 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Mar 21 09:16:29 2023 -0700 |
| tree | 20741abe1df7fea205717875ba646ccd0bbd873a | |
| parent | b079fd3182c2bb9b17c60d1b663e55d153fcc9b6 [diff] |
Clean up the Bazel JUnit test runner To remove a dependency on Dagger quickly, the auto-generated boilerplate code was checked-in[1]. Since we are no longer using any dependency injection, most of the indirection with modules, suppliers/providers, etc are of no value. This change also removes the duplication in `JUnit4BazelMock` by moving the test overrides into `JUnit4RunnerModule` / `JUnit4RunnerTest$TestModule` [1] https://github.com/bazelbuild/bazel/commit/225f69fc83bf9cab6cf4ee3871e633efd96fdb33 PiperOrigin-RevId: 518291786 Change-Id: I1b4ea99a0d4b5f0265fb98d98618e6232e247698
{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
