Fixing false positives for MISRA C++ 2023 Rule 6.5.1 on googletest ma… #8086
+5
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Contributor
Author
|
This is a follow-up for #8081, which didn't provide a proper fix. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When running cppcheck premium with MISRA C++2023 Rule 6.5.1 enabled on unittests using googletests with
--library=googletest, cppcheck is flagging eachTEST(test_suite_name, test_name)with violation of Rule 6.5.1.The current definition of
TEST(A,B)ingoogletest.cfgdefines the function without special care, which violates the MISRA rule.Following the original MACRO definition from googletest, the PR introduces encapsulation with a class.