Is it possible to generate a kind of report document maybe using some scripts (python scripts) for generating a report of the technical debt ?
Is it also possible to track things like code coverage code duplication and other things ?
Please let me know
Thanks a lot
Simone
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Cppcheck is focused on static analysis with a focus on dangerous code.
Technical debt; a copy/paste detector and some code metrics tool? I can't recommend a tool. I believe Cppcheck addons for this could be interesting. I know people worked on a code quality metrics addon in ~ july / august but did not hear about what progress they made..
Code coverage; There are tools for this but I'd rather not recommend a tool.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For generating reports I tend to abuse doxygen for that. I can't remember what version of doxygen started supporting markdown. What I normally do is run all the test/tools in the CI system and then parse their output into markdown. After that I run doxygen all the way to pdf. With a bit of tweaking I can get a nice report.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi forum ...
Is it possible to generate a kind of report document maybe using some scripts (python scripts) for generating a report of the technical debt ?
Is it also possible to track things like code coverage code duplication and other things ?
Please let me know
Thanks a lot
Simone
Cppcheck is focused on static analysis with a focus on dangerous code.
Technical debt; a copy/paste detector and some code metrics tool? I can't recommend a tool. I believe Cppcheck addons for this could be interesting. I know people worked on a code quality metrics addon in ~ july / august but did not hear about what progress they made..
Code coverage; There are tools for this but I'd rather not recommend a tool.
When looking for C++ tools I often find this git book on C++ best practices by Jason Turner a good place to start. The author has a section dedicated to C++ tools https://github.com/cpp-best-practices/cppbestpractices/blob/master/02-Use_the_Tools_Available.md Since it is a git book it is being periodically updated.
For generating reports I tend to abuse doxygen for that. I can't remember what version of doxygen started supporting markdown. What I normally do is run all the test/tools in the CI system and then parse their output into markdown. After that I run doxygen all the way to pdf. With a bit of tweaking I can get a nice report.