Best Procedure to follow to test a change to cppcheck
Static source code analysis tool for C and C++ code
Brought to you by:
danielmarjamaki
Menu
▾
▴
I was wondering what is the best process to follow to test a change to cppcheck?
Right now I'm just making sure it matches the previous output. I have a feeling there is a way to run internal testing.
Use the script cppcheck/tools/test-my-pr.py
You don't need to have a github PR. But you need to have your changes committed in a git branch. You run the script while your development branch is checked out.
I posted my question separately-- "two cppcheck commits, same debian source --> one cppcheck commit, two debian sources"
Last edit: Jason Reich 2023-08-17
I use a little bash scripting and git blame. If your code is in git repo this might help you. I do this will all CI tools not just cppcheck. The main reason for this is for upgrading CI tools or remove false positives if necessary. So I can push the new version into CI before fixing all the new things it found so that developers get the benefits of the upgrade tool right away. I use git blame -n pared with the cppcheck( or any tools )output. That way I have a list of things that I can filter out of a tools output.