Lines Matching +refs:cc +refs:include +refs:needs

363 #include <ostream>
693 path/to/foo_test.cc:11: Failure
698 path/to/foo_test.cc:17: A
700 path/to/foo_test.cc:12: Failure
875 >     needs to be prefixed with `::testing::Test::` if used outside of the
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…
1400 put the above code in a header file, you can `#include` it in multiple C++
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
1468     clients aren't allowed to include this header but your tests can. Such is
1492     // foo_test.cc
1689 listen to include the start and end of the test program, a test suite, or a test
1703 implementation of all methods in the interface, such that a subclass only needs
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_…
1920 To include disabled tests in test execution, just invoke the test program with
1987 your test runner (not part of GoogleTest) needs to do the following: