diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 2c47d21213c..f8cf2361a5e 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -179,7 +179,7 @@ All new code should follow the folder structure.
 ## Testing
 
 We use [Google test](https://github.com/google/googletest) for our unit and integration tests. We require compatibility
-with the version 1.8.1.
+with the version 1.10.0.
 
 Have a look at our [best practice guidelines](./doc/website/advanced/best-practice-for-testing.md) for writing tests and
 [installation guide for contributors](./doc/website/advanced/installation-guide-for-contributors.md#build-and-run-tests) for building them.
diff --git a/doc/website/advanced/best-practice-for-testing.md b/doc/website/advanced/best-practice-for-testing.md
index d75869e6e06..daaad219fdc 100644
--- a/doc/website/advanced/best-practice-for-testing.md
+++ b/doc/website/advanced/best-practice-for-testing.md
@@ -230,7 +230,7 @@ They also exert all the good practices mentioned previously, like clear and dist
 There are situations when test cases only vary in the type applied to the `sut`. In this case typed tests can be used to reduce repetition.
 The there is a section for [typed tests](https://github.com/google/googletest/blob/master/docs/advanced.md#typed-tests) in the advanced gtest documentation.
 
-A more thorough [example](https://github.com/google/googletest/blob/release-1.8.1/googletest/samples/sample6_unittest.cc) is in the gtest github repository.
+A more thorough [example](https://github.com/google/googletest/blob/release-1.10.0/googletest/samples/sample6_unittest.cc) is in the gtest github repository.
 
 ## Parameterized Tests
 
@@ -245,7 +245,7 @@ The block post mentions tuples to pass multiple parameters at once. Since tuples
 
 Some classes are hard to test or to reach a full coverage. This might be due to external access or interaction with the operating system.
 Mocks can help to have full control over the `sut` and reliably cause error conditions to test the negative code path.
-There is an [extensive gmock documentation](https://github.com/google/googletest/tree/release-1.8.1/googlemock/docs) in the gtest github repository.
+There is an [extensive gmock documentation](https://github.com/google/googletest/tree/release-1.10.0/googlemock/docs) in the gtest github repository.
 
 ## Pitfalls
 Some tests require creating dummy classes and it might be that the same name is chosen multiple times, e.g. “class DummyData {...};”.