Lines Matching full:googletest

1 # GoogleTest Primer
3 ## Introduction: Why GoogleTest?
5 *GoogleTest* helps you write better C++ tests.
7 GoogleTest is a testing framework developed by the Testing Technology team with
9 Linux, Windows, or a Mac, if you write C++ code, GoogleTest can help you. And it
12 So what makes a good test, and how does GoogleTest fit in? We believe:
15     that succeeds or fails as a result of other tests. GoogleTest isolates the
17     GoogleTest allows you to run it in isolation for quick debugging.
19     code. GoogleTest groups related tests into test suites that can share data
24     platform-neutral; its tests should also be platform-neutral. GoogleTest
26     exceptions, so GoogleTest tests can work with a variety of configurations.
28     as possible. GoogleTest doesn't stop at the first test failure. Instead, it
34     and let them focus on the test *content*. GoogleTest automatically keeps
37 6.  Tests should be *fast*. With GoogleTest, you can reuse shared resources
41 Since GoogleTest is based on the popular xUnit architecture, you'll feel right
51 Historically, GoogleTest started to use the term *Test Case* for grouping
57 The related term *Test*, as it is used in GoogleTest, corresponds to the term
64 GoogleTest recently started replacing the term *Test Case* with *Test Suite*.
71 Meaning                                                                              | GoogleTest T…
81 When using GoogleTest, you start by writing *assertions*, which are statements
101 GoogleTest assertions are macros that resemble function calls. You test a class
103 GoogleTest prints the assertion's source file and line number location, along
105 be appended to GoogleTest's message.
138 GoogleTest provides a collection of assertions for verifying the behavior of
143 provided by GoogleTest, see the [Assertions Reference](reference/assertions.md).
152     use the various GoogleTest assertions to check values.
193 GoogleTest groups the test results by test suites, so logically related tests
247 For each test defined with `TEST_F()`, GoogleTest will create a *fresh* test
251 GoogleTest always deletes a test fixture before it creates the next one.
252 GoogleTest does **not** reuse the same test fixture for multiple tests. Any
328 1.  GoogleTest constructs a `QueueTest` object (let's call it `t1`).
340 `TEST()` and `TEST_F()` implicitly register their tests with GoogleTest. So,
351 *   Saves the state of all GoogleTest flags.
363 *   Restores the state of all GoogleTest flags.
377 > once conflicts with some advanced GoogleTest features (e.g., thread-safe
459 GoogleTest flags, and removes all recognized flags. This allows the user to