Add TESTBRIDGE_TEST_RUNNER_FAIL_FAST to JUnit4 - Suppport Bazel protocol for stopping test runner execution upon first failure. - Reduces test failure result latency by returning the test action as soon as it fails - Implemented using TESTBRIDGE env variable (similar to --testonly flag) - Important behavior change in StoppedUserException handling: no longer propagates the exception. This is done so that tests still generates test.xml output Bazel flag: --test_runner_fail_fast Environment variable: TESTBRIDGE_TEST_RUNNER_FAIL_FAST=1 Change on test runners: Stop and return upon first test failure if TESTBRIDGE_TEST_FAIL_FAST=1 PiperOrigin-RevId: 297681623
{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
