Lines Matching +refs:cc +refs:check +refs:includes

30 run into. Therefore, sometimes a user has to use `EXPECT_TRUE()` to check a
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
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.
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
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_…
1969 Therefore you'll get a different order every time. The console output includes
2388 finished. Then, the test runner can check if this file exists. In case the file