Resolve clang-tidy warnings in test files#316
Merged
PLeVasseur merged 41 commits intoeclipse-uprotocol:mainfrom Apr 16, 2025
Merged
Resolve clang-tidy warnings in test files#316PLeVasseur merged 41 commits intoeclipse-uprotocol:mainfrom
PLeVasseur merged 41 commits intoeclipse-uprotocol:mainfrom
Conversation
…HROW, ASSERT_THROW, ASSERT_NO_THROW)
|
Code coverage report is ready! 📈
|
PLeVasseur
approved these changes
Apr 16, 2025
Contributor
PLeVasseur
left a comment
PLeVasseur
left a comment
There was a problem hiding this comment.
Nice @lennartbecker-d! Thanks for contributing these fixes
This was referenced May 21, 2025
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
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.
This pull request addresses and resolves several clang-tidy warnings identified in the test files.
The the clang-tidy.sh script is also modified to check test files additionaly to include/* and src/*. Previously, this was uncommented in #310.
As there are no more linter warnings remaining, #272, #264 and #262 seem to be resolved in the beforegoing PR and should be closed as well.
Closes #311 #274 #273 #271 #270 #269 #268 #267 #266 #265