That’s great. While you’re looking at it though, try to make the tutorial about the ROS specific aspects and link out to other upstream gtest tutorials for the core gtest concepts instead of reproducing them.
The Troubleshooting and Review pages are not completely auto generated, but are auto linked to the header if they are present. They have templates for them if you create the page. The TroubleshootingTemplate just helps start a list with reasonable formatting. The Reviews page is left over from the older QAProcess used at Willow Garage. It hasn’t been used really since then. Much of that process was used on the old wiki and the Review pages were found to be slowing down the wiki and often would overshadow formal documentation in search results. Much of that content predates the use of github and other platforms with pull requests and review processes available. It’s likely that all of the QAProcess should be cleaned up. As an example the gtest Review page was made to propose creating a ROS package for gtest, but clearly we’ve chosen to use the upstream version now so that proposal from 2009 is not particularly useful now and could be cleared out.
Since the Troubleshooting page had zero content I just deleted it.
We should not delete the rosbuild content, but I wouldn’t suggest spending much time to update it to new practices as we are not planning to spend time updating the rosbuild toolchain.