Lines Matching refs:code

17 User code is *prohibited* from using such identifiers.
109 *   Value-parameterized tests can be easier to write if you need different code
201 Otherwise your code is **invalid C++**, and may break in unexpected ways. In
233 Typically, your code looks like this:
352     GoogleTest assertions in a destructor if your code could run on such a
381 code will no longer be able to ignore `RUN_ALL_TESTS()` when compiled with
389 case, the code was already broken in the first place, so we didn't break it. :-)
621 ## How can my code detect if it is running in a test?
623 If you write code that sniffs whether it's running in a test and does different
624 things accordingly, you are leaking test-only logic into production code and
625 there is no easy way to ensure that the test-only code paths aren't run by
630 In general, the recommended way to cause the code to behave differently under
632 different functionality from the test and from the production code. Since your
633 production code doesn't link in the for-test logic at all (the
640 whether the code is under test.
646 better than commenting out the code or using `#if 0`, as disabled tests are
674 However, the following code is **not allowed** and will produce a runtime error