Lines Matching +full:sometimes +full:- +full:uninitialized

7 [the `DISABLED_` prefix](advanced.md#temporarily-disabling-tests), in addition
13 1.  any identifier that starts with an `_` followed by an upper-case letter, and
25 1.  If `TestSuiteName` starts with an `_` followed by an upper-case letter (say,
36 (Actually, `TestSuiteName` can start with `_` -- as long as the `_` isn't
37 followed by an upper-case letter. But that's getting complicated. So for
68 Due to some peculiarity of C++, it requires some non-trivial template meta
72 error-prone than necessary).
97 … interface satisfy some common requirements. Should I use typed tests or value-parameterized tests?
100 value-parameterized tests can get it done. It's really up to you the user to
109 *   Value-parameterized tests can be easier to write if you need different code
116     Value-parameterized tests only show the number of the failed iteration by
124     when using value-parameterized tests.
126 I hope I didn't confuse you more. :-) If you don't mind, I'd suggest you to give
131 ## I got some run-time errors about invalid proto descriptors when using `ProtocolMessageEquals`. H…
141 will now get run-time errors like:
154 Death tests (`EXPECT_DEATH`, etc) are executed in a sub-process s.t. the
156 result, any in-memory side effects they incur are observable in their respective
157 sub-processes, but not in the parent process. You can think of them as running
204 doesn't mean it's valid. It just means that you were lucky. :-)
223 one test suite can use a particular fixture. Sometimes, however, multiple test
247     ... additional set-up work ...
251     ... clean-up work for FooTest ...
277 [here](advanced.md#assertion-placement).
279 ## My death test hangs (or seg-faults). How do I fix it?
291 Sometimes this is impossible as some library you must use may be creating
298 If you go with thread-safe death tests, remember that they rerun the test
300 program can run side-by-side with itself and is deterministic.
304 bullet - sorry!
313 When you need to write per-test set-up and tear-down logic, you have the choice
333     derived class constructor has a chance to run is very dangerous - the
334     virtual method might operate on uninitialized data. Therefore, if you need
338     `ASSERT_xx` macros. Therefore, if the set-up operation could cause a fatal
342 *   If the tear-down operation could throw an exception, you must use
350     client-side), which will eliminate the need for the user to propagate
389 case, the code was already broken in the first place, so we didn't break it. :-)
404 [section](advanced.md#assertion-placement) in the user's guide explains it.
408 C++ is case-sensitive. Did you spell it as `Setup()`?
410 Similarly, sometimes people spell `SetUpTestSuite()` as `SetupTestSuite()` and
445 The GoogleTest output is meant to be a concise and human-friendly report. If
527 *   If you explicitly declare a non-default constructor for class `FooTest`
530 *   If `FooTest` has a const non-static data member, then you have to define the
554 the test case would require multiple set-up and tear-down processes, which is
573 …g my entire test suite \*DeathTest when it contains both death tests and non-death tests. What do …
600 after the fork-and-exec-style death tests are implemented.
604 If you use a user-defined type `FooType` in an assertion, you must make sure
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
633 production code doesn't link in the for-test logic at all (the
634 [`testonly`](http://docs.bazel.build/versions/master/be/common-definitions.html#common.testonly) at…
650 the `--gtest_also_run_disabled_tests` flag.