Lines Matching +refs:cc +refs:check +refs:functions

30 run into. Therefore, sometimes a user has to use `EXPECT_TRUE()` to check a
57 `AssertionResult` using one of these factory functions:
154 avoid an explosion of new macros, we provide them as predicate-format functions
243 void-returning functions. This is a consequence of Google's not using
260 NOTE: Constructors and destructors are not considered void-returning functions,
279 to check for preconditions of the system under test during runtime and skip
625 your program will fail the heap check as the parent process will never see the
643 Note: If you want to put a series of test assertions in a subroutine to check
693 path/to/foo_test.cc:11: Failure
698 path/to/foo_test.cc:17: A
700 path/to/foo_test.cc:12: Failure
813 functions to catch fatal failures in a sub-routine and return early.
1114 functions for generating test parameters—see details at
1180 where the list of test cases is dynamic and may be empty, then this check can be
1187 You can see [sample7_unittest.cc] and [sample8_unittest.cc] for more examples.
1189 [sample7_unittest.cc]: https://github.com/google/googletest/blob/main/googletest/samples/sample7_un…
1190 [sample8_unittest.cc]: https://github.com/google/googletest/blob/main/googletest/samples/sample8_un…
1208 2.  Put the `TEST_P` definitions in `foo_param_test.cc`, which includes
1213 contains `foo_param_test.cc`. You can instantiate the same abstract test suite
1339 You can see [sample6_unittest.cc] for a complete example.
1341 [sample6_unittest.cc]: https://github.com/google/googletest/blob/main/googletest/samples/sample6_un…
1420 You can see [sample6_unittest.cc] for a complete example.
1438 *   Static functions ( *not* the same as static member functions!) or unnamed
1444 *   Both static functions and definitions/declarations in an unnamed namespace
1446     `#include` the entire `.cc` file being tested in your `*_test.cc` file.
1447     (#including `.cc` files is not a good way to reuse code - you should not do
1453     Your production `.cc` files and your tests are allowed to include this
1492     // foo_test.cc
1683 functions called from them.
1778 details, see [sample9_unittest.cc].
1780 [sample9_unittest.cc]: https://github.com/google/googletest/blob/main/googletest/samples/sample9_un…
1805 See [sample10_unittest.cc] for an example of a failure-raising listener.
1807 [sample10_unittest.cc]: https://github.com/google/googletest/blob/main/googletest/samples/sample10_…
1983 want to run the test functions in parallel and get the result faster. We call
1996     environment variables, it will select a subset of the test functions to run.
2010 that contains the following 5 test functions:
2020 Suppose you have 3 machines at your disposal. To run the test functions in
2123 *   `<testcase>` elements correspond to GoogleTest test functions.
2156     many test functions the GoogleTest program or test suite contains, while the
2388 finished. Then, the test runner can check if this file exists. In case the file
2426 all provide weak functions that you can override to trigger explicit failures
2428 To override these functions, place definitions for them in a source file that