Comprehensive Use of Analyzers to Improve Code Quality
summary
The talk explains how to combine multiple code-analysis tools—static analyzers, sanitizers, compilers, coverage tools, etc.—into a single, unified workflow by ingesting their heterogeneous reports into SonarQube. It covers practical integration examples showing how SonarQube can serve as a central platform to collect and consistently work with findings from different tools rather than relying on a single "silver-bullet" analyzer.
AI-written summary · about
chapters (13)
- 0:00Code quality tools intro
- 6:53Static analysis vs review
- 10:08Code smells impact
- 15:33Code metrics and defects
- 20:01Setting up SonarQube
- 24:26Integrating analyzers
- 27:46Clang dynamic analysis
- 30:53Valgrind memory leaks
- 32:19gcov coverage
- 34:11SonarQube results
- 36:25Tracking quality over time
- 37:06Summary
- 38:11Q&A
related talks
41mSonar...Qube, the story of a little code analyzer that grows up
46mIn search of Clean Code with Sonar, 20,000 leagues under an ocean of code!
27mScaling Software Integrity with Automated Code Verification
17mSource Code Analyzer
53mStatic Analysis Tools: QA’s Best Friend
20mHow to Manage Software Architecture with SonarQube
54mA Shock to the System Static Analysis for Real AppSec
30mAn Extensible Feature-Oriented Approach for Fine-Grained Code Quality Analysis