mirror of
https://github.com/google/googletest.git
synced 2025-12-06 08:46:50 +08:00
17d335d7c7
For `EXPECT_THAT` matcher usage, showing only the first failure meant that users would sometimes have to make a fix and run the test again only to notice that there's another failure. It's better to show more failures so that the user can fix several issues in one go. In practice, very little code actually wants the short circuiting here, only a handful of cases with custom matchers used like `AllOf(BoundsCheck(), UncheckedAccess())`. These cases are fixable by refactoring `UncheckedAccess()` to instead also apply a bounds check to fail the matcher rather than crash. Notably, this change doesn't affect `AnyOf`, so another workaround is to change `AllOf(m1, m2, ...)` into `Not(AnyOf(Not(m1), Not(m2), ...))`. PiperOrigin-RevId: 826316273 Change-Id: Ie8186f75c10443d8da35b5d07b6a8cd9ae85b451 |
||
|---|---|---|
| .. | ||
| BUILD.bazel | ||
| gmock_all_test.cc | ||
| gmock_ex_test.cc | ||
| gmock_leak_test_.cc | ||
| gmock_leak_test.py | ||
| gmock_link2_test.cc | ||
| gmock_link_test.cc | ||
| gmock_link_test.h | ||
| gmock_output_test_.cc | ||
| gmock_output_test_golden.txt | ||
| gmock_output_test.py | ||
| gmock_stress_test.cc | ||
| gmock_test_utils.py | ||
| gmock_test.cc | ||
| gmock-actions_test.cc | ||
| gmock-cardinalities_test.cc | ||
| gmock-function-mocker_test.cc | ||
| gmock-internal-utils_test.cc | ||
| gmock-matchers_test.h | ||
| gmock-matchers-arithmetic_test.cc | ||
| gmock-matchers-comparisons_test.cc | ||
| gmock-matchers-containers_test.cc | ||
| gmock-matchers-misc_test.cc | ||
| gmock-more-actions_test.cc | ||
| gmock-nice-strict_test.cc | ||
| gmock-port_test.cc | ||
| gmock-pp_test.cc | ||
| gmock-pp-string_test.cc | ||
| gmock-spec-builders_test.cc | ||