From 555486f408ab4906118eddf11c856da7f8690f14 Mon Sep 17 00:00:00 2001 From: Abseil Team Date: Tue, 28 Feb 2023 08:16:34 -0800 Subject: [PATCH] Rephrase the description of TEST_F() arguments for clarity. PiperOrigin-RevId: 512937964 Change-Id: Ifa6369a80dc7d8efe60511417496d58317cfc28d --- docs/primer.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/primer.md b/docs/primer.md index 80c2d0a691..d559fe84fc 100644 --- a/docs/primer.md +++ b/docs/primer.md @@ -227,14 +227,14 @@ When using a fixture, use `TEST_F()` instead of `TEST()` as it allows you to access objects and subroutines in the test fixture: ```c++ -TEST_F(TestFixtureName, TestName) { +TEST_F(TestFixtureClassName, TestName) { ... test body ... } ``` -Like `TEST()`, the first argument is the test suite name, but for `TEST_F()` -this must be the name of the test fixture class. You've probably guessed: `_F` -is for fixture. +Unlike `TEST()`, in `TEST_F()` the first argument must be the name of the test +fixture class. (`_F` stands for "Fixture"). No test suite name is specified for +this macro. Unfortunately, the C++ macro system does not allow us to create a single macro that can handle both types of tests. Using the wrong macro causes a compiler