Nathan Froyd 0544a4cf70 Bug 1434671 - add a benchmarking macro permitting custom test fixtures; r=ted.mielczarek ... GTest supports the TEST macro, which just runs a bunch of tests, and the TEST_F macro, which enables writing custom test fixtures to perform per-test setup and teardown. The benchmarking framework we have has a corresponding macro for the former, but no corresponding macro for the latter. If there's significant work to be done during setup and teardown, we certainly don't want to be doing that work during the actual benchmarking! So let's introduce a MOZ_GTEST_BENCH_F macro that works similarly to the TEST_F macro.		2018-02-26 17:31:58 -04:00
..
benchmark	Bug 1396208 - For benchmarking, add a black box function that is opaque to the optimizer. r=froydnj	2017-10-10 09:48:26 +03:00
gmock	Bug 1343557 - Update gtest and gmock to 1.7.0; r=ted.mielczarek	2017-03-02 08:59:50 -05:00
gtest	Bug 1406687 Pass return values from fwrite to Unused to silence the warn-unused-result warning r=njn	2017-10-09 15:01:48 -05:00
mozilla	Bug 1434671 - add a benchmarking macro permitting custom test fixtures; r=ted.mielczarek	2018-02-26 17:31:58 -04:00
Makefile.in	Bug 992983 - Build and upload the gtest libxul during test packaging. r=ted	2015-07-16 16:52:31 -07:00
MozGtestFriend.h	…
bench.py	Bug 1394604 - Avoid direct path to python3 in bench script. r=froydnj	2017-08-30 10:34:00 -04:00
moz.build	Bug 1396208 - For benchmarking, add a black box function that is opaque to the optimizer. r=froydnj	2017-10-10 09:48:26 +03:00
rungtests.py	Bug 1322616 - Report unique message for gtest output timeout; r=jmaher	2017-12-05 15:43:03 -07:00