Lines Matching +full:board +full:- +full:related

19     code. GoogleTest groups related tests into test suites that can share data
24     platform-neutral; its tests should also be platform-neutral. GoogleTest
30     tests that report non-fatal failures after which the current test continues.
31     Thus, you can detect and fix multiple bugs in a single run-edit-compile
38     across tests and pay for the set-up/tear-down only once, without making
52 related tests, whereas current publications, including International Software
53 Testing Qualifications Board ([ISTQB](https://www.istqb.org/)) materials and
57 The related term *Test*, as it is used in GoogleTest, corresponds to the term
72 :----------------------------------------------------------------------------------- | :-----------…
73 …am path with specific input values and verify the results | [TEST()](#simple-tests) | [Test Case][…
76 [istqb test case]: https://glossary.istqb.org/en_US/term/test-case-2
77 [istqb test suite]: https://glossary.istqb.org/en_US/term/test-suite-1-3
116 possibly skipping clean-up code that comes after it, it may cause a space leak.
117 Depending on the nature of the leak, it may or may not be worth fixing - so keep
134 macro--in particular, C strings and `string` objects. If a wide string
136 streamed to an assertion, it will be translated to UTF-8 when printed.
140 based on relational operators, verify string values, floating-point values, and
154     test fails (either fatally or non-fatally), or if the test crashes, the
193 GoogleTest groups the test results by test suites, so logically related tests
205 ## Test Fixtures: Using the Same Data Configuration for Multiple Tests {#same-data-multiple-tests}
214     we'll want to access fixture members from sub-classes.
218     **`Setup()`** with a small `u` - Use `override` in C++11 to make sure you
340 unlike with many other C++ testing frameworks, you don't have to re-list all
345 `RUN_ALL_TESTS()` runs *all tests* in your link unit--they can be from different
376 > once conflicts with some advanced GoogleTest features (e.g., thread-safe
377 > [death tests](advanced.md#death-tests)) and thus is not supported.
410      // You can do set-up work for each test here.
414      // You can do clean-up work that doesn't throw exceptions here.
476 *   Google Test is designed to be thread-safe. The implementation is thread-safe
482     `gtest-port.h` for your platform.