When we run clang-tidy on our source code, it finds hundreds of issues related to usages of gtest. We currently have to disable a few clang-tidy checks because of this. In the longer run, we want to enable these checks again. I believe the reported issues are false positives, so it would be beneficial for us if gtest would suppress these warnings.
I found out (among others in https://github.com/google/googletest/issues/853) that gtest already contains 'NOLINT' comments to suppress clang-tidy warnings. I would like to point out a few additional places to add them (based on the code in version 1.8.1):
If I can help out in any other way, let me know.
Two more I hit:
cppcoreguidelines-owning-memorycppcoreguidelines-special-member-functionsOne more:
cppcoreguidelines-avoid-non-const-global-variables
Most helpful comment
Two more I hit:
cppcoreguidelines-owning-memorycppcoreguidelines-special-member-functions