From 109f848bc83f6618bb12c15e92ea17d0cbba3c54 Mon Sep 17 00:00:00 2001 From: Gennadiy Civil Date: Mon, 11 Jun 2018 11:54:27 -0400 Subject: Rename Samples.md to samples.md and adjust the links --- googletest/docs/Documentation.md | 2 +- googletest/docs/Samples.md | 14 -------------- googletest/docs/primer.md | 2 +- googletest/docs/samples.md | 14 ++++++++++++++ 4 files changed, 16 insertions(+), 16 deletions(-) delete mode 100644 googletest/docs/Samples.md create mode 100644 googletest/docs/samples.md diff --git a/googletest/docs/Documentation.md b/googletest/docs/Documentation.md index b6c77af1..6c3bf7a5 100644 --- a/googletest/docs/Documentation.md +++ b/googletest/docs/Documentation.md @@ -5,7 +5,7 @@ documentation for that specific version instead (e.g. by checking out the respective git branch/tag).** * [Primer](primer.md) -- start here if you are new to Google Test. - * [Samples](Samples.md) -- learn from examples. + * [Samples](samples.md) -- learn from examples. * [AdvancedGuide](advanced.md) -- learn more about Google Test. * [XcodeGuide](XcodeGuide.md) -- how to use Google Test in Xcode on Mac. * [Frequently-Asked Questions](faq.md) -- check here before asking a question on the mailing list. diff --git a/googletest/docs/Samples.md b/googletest/docs/Samples.md deleted file mode 100644 index f21d2005..00000000 --- a/googletest/docs/Samples.md +++ /dev/null @@ -1,14 +0,0 @@ -If you're like us, you'd like to look at some Google Test sample code. The -[samples folder](../samples) has a number of well-commented samples showing how to use a -variety of Google Test features. - - * [Sample #1](../samples/sample1_unittest.cc) shows the basic steps of using Google Test to test C++ functions. - * [Sample #2](../samples/sample2_unittest.cc) shows a more complex unit test for a class with multiple member functions. - * [Sample #3](../samples/sample3_unittest.cc) uses a test fixture. - * [Sample #4](../samples/sample4_unittest.cc) is another basic example of using Google Test. - * [Sample #5](../samples/sample5_unittest.cc) teaches how to reuse a test fixture in multiple test cases by deriving sub-fixtures from it. - * [Sample #6](../samples/sample6_unittest.cc) demonstrates type-parameterized tests. - * [Sample #7](../samples/sample7_unittest.cc) teaches the basics of value-parameterized tests. - * [Sample #8](../samples/sample8_unittest.cc) shows using `Combine()` in value-parameterized tests. - * [Sample #9](../samples/sample9_unittest.cc) 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](../samples/sample10_unittest.cc) shows use of the listener API to implement a primitive memory leak checker. diff --git a/googletest/docs/primer.md b/googletest/docs/primer.md index 48ce894e..52b99f96 100644 --- a/googletest/docs/primer.md +++ b/googletest/docs/primer.md @@ -522,7 +522,7 @@ There is one more pitfall, though. If you use Google Test as a static library (t # Where to Go from Here # Congratulations! You've learned the Google Test basics. You can start writing -and running Google Test tests, read some [samples](Samples.md), or continue with +and running Google Test tests, read some [samples](samples.md), or continue with [AdvancedGuide](advanced.md), which describes many more useful Google Test features. # Known Limitations # diff --git a/googletest/docs/samples.md b/googletest/docs/samples.md new file mode 100644 index 00000000..f21d2005 --- /dev/null +++ b/googletest/docs/samples.md @@ -0,0 +1,14 @@ +If you're like us, you'd like to look at some Google Test sample code. The +[samples folder](../samples) has a number of well-commented samples showing how to use a +variety of Google Test features. + + * [Sample #1](../samples/sample1_unittest.cc) shows the basic steps of using Google Test to test C++ functions. + * [Sample #2](../samples/sample2_unittest.cc) shows a more complex unit test for a class with multiple member functions. + * [Sample #3](../samples/sample3_unittest.cc) uses a test fixture. + * [Sample #4](../samples/sample4_unittest.cc) is another basic example of using Google Test. + * [Sample #5](../samples/sample5_unittest.cc) teaches how to reuse a test fixture in multiple test cases by deriving sub-fixtures from it. + * [Sample #6](../samples/sample6_unittest.cc) demonstrates type-parameterized tests. + * [Sample #7](../samples/sample7_unittest.cc) teaches the basics of value-parameterized tests. + * [Sample #8](../samples/sample8_unittest.cc) shows using `Combine()` in value-parameterized tests. + * [Sample #9](../samples/sample9_unittest.cc) 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](../samples/sample10_unittest.cc) shows use of the listener API to implement a primitive memory leak checker. -- cgit v1.2.3