Commits · a5308bb992c049b16b763f8910da70c208c5cede · yangql / googletest

20 Apr, 2023 1 commit

Tom Hughes authored Apr 20, 2023

PiperOrigin-RevId: 525850646
Change-Id: I64387f5b933beb79cd05636dca81b7a75213383e

a5308bb9

01 Feb, 2023 1 commit

Fix include order · ebedaa18

Tom Hughes authored Feb 01, 2023

PiperOrigin-RevId: 506424617
Change-Id: If7f0beb92022589523db204a6b5cbe9249cebf62

ebedaa18

30 Jan, 2023 1 commit

Use GTEST_DISABLE_MSC_WARNINGS macros to disable warnings · 4fb7039f

Tom Hughes authored Jan 30, 2023

Prior to this change we had a mixture of pragmas and
GTEST_DISABLE_MSC_WARNINGS; this change consolidates all instances
to use the macros.

PiperOrigin-RevId: 505786926
Change-Id: I2be8f6304387393995081af42ed32c2ad1bba5a7

4fb7039f

24 Jan, 2023 1 commit

Remove FloatingPoint::Max() in favor of std::numeric_limits::max() · 544c96ed

Derek Mauro authored Jan 24, 2023

In #4113 a user says Max clashes with a macro. Since it is only used in
a test, use std::numeric_limits::max() instead.

Note that in headers, the macro issue can be mitigated with
parenthesis like this: `(std::numeric_limits<T>::max)()`

PiperOrigin-RevId: 504284906
Change-Id: Ibf430caec1a6afdf6b303534fec6a4fd00a6373f

544c96ed

26 Apr, 2022 1 commit
- Generalize gmock-matchers_test to handle is_gtest_matcher-style matchers, too. · 238e4745
  Abseil Team authored Apr 26, 2022
```
PiperOrigin-RevId: 444586594
Change-Id: I0de9b40b3773e3047a492f050266967ea935ae3e
```
  238e4745
22 Apr, 2022 1 commit
- Remove the legacy internal GTEST_DISALLOW_* macros · bf66935e
  Derek Mauro authored Apr 22, 2022
```
PiperOrigin-RevId: 443715444
Change-Id: I3ffd54b63d2728ae4a668ee7875c8c3c8188087c
```
  bf66935e
23 Mar, 2022 1 commit

Split gmock-matchers_test into 4 smaller test #3653 · 07329346

Mattias Ellert authored Mar 23, 2022

The one large test does not link in limited memory environments

Closes #3653

PiperOrigin-RevId: 436753193
Change-Id: Idd59b6509994fc642147b88279ee791cd1d7bdd0

07329346