9b5028523f
Snapshotted from 5e7fd50e17b6edf1cadff973d0ec68966cf3265e in the upstream repository: https://github.com/google/googletest Since standalone builds and bots will need this, checking in a copy rather than require everyone use gclient, repo, git submodules or scary CMake scripts is probably simplest. Consumers with their own copies of googletest will likely wish to ignore or even exclude this directory. BUG=129 Change-Id: If9f4cec5ae0d7a3976dcfffd1ead6950ef7b7c4e Reviewed-on: https://boringssl-review.googlesource.com/13229 Reviewed-by: David Benjamin <davidben@google.com>
1.3 KiB
1.3 KiB
If you're like us, you'd like to look at some Google Test sample code. The samples folder has a number of well-commented samples showing how to use a variety of Google Test features.
- Sample #1 shows the basic steps of using Google Test to test C++ functions.
- Sample #2 shows a more complex unit test for a class with multiple member functions.
- Sample #3 uses a test fixture.
- Sample #4 is another basic example of using Google Test.
- Sample #5 teaches how to reuse a test fixture in multiple test cases by deriving sub-fixtures from it.
- Sample #6 demonstrates type-parameterized tests.
- Sample #7 teaches the basics of value-parameterized tests.
- Sample #8 shows using
Combine()in value-parameterized tests. - Sample #9 shows use of the listener API to modify Google Test's console output and the use of its reflection API to inspect test results.
- Sample #10 shows use of the listener API to implement a primitive memory leak checker.