SonarQube is NOT a Code Coverage Tool скачать в хорошем качестве

SonarQube is NOT a Code Coverage Tool

"SonarQube Does Code Coverage!" - a DevOps Comedy Special Asked this Question, during hundreds of interviews for Senior DevOps/ DevOps lead positions ... "What does SonarQube do?" "It does code coverage" (WRONG WRONG WRONG ) DevOps Engineer: "I configured SonarQube! Where's my coverage?" SonarQube: (Politely) "I'm waiting for the coverage report..." Engineer: "What report?" SonarQube: "The one from JaCoCo?" Engineer: "Who's JaCoCo?" JaCoCo: (From the back) "I've been here the whole time! You never called me!" Engineer: "I thought SonarQube did everything!" SonarQube: "I'm flattered, but no. I'm more of a coordinator. Like a project manager who doesn't actually do the work but makes great PowerPoints." The reality check : SonarQube Doesn't Calculate Your Code Coverage. Here's What It Actually Does. SonarQube is designed to consume and display coverage data, not to generate it. At its core, SonarQube is a quality intelligence platform, not a coverage generation tool. Its primary role is to aggregate, analyze, and visualize a wide range of code quality metrics that are produced by other specialized tools. It consumes data from linters, static analyzers, and, most importantly for this topic, code coverage tools. Then who generates the Code Coverage? Watch Video- how to integrate them in CI/CD Pipeline. Java/Kotlin → JaCoCo, Cobertura JavaScript/TypeScript → Istanbul/NYC, Jest Python → pytest-cov, coverage.py .NET/C# → Coverlet, OpenCover Go → Built-in coverage, gocover-cobertura Ruby → SimpleCov, RCov PHP → PHPUnit coverage, PCOV Swift/iOS → Xcode coverage, Slather Rust → cargo-tarpaulin, grcov Scala → scoverage, JaCoCo Android → JaCoCo, Kover React → Jest coverage, Istanbul Node.js → NYC, c8 Angular → Karma + Istanbul, Jest Vue.js → Jest, Istanbul Dart/Flutter → flutter test --coverage, lcov Groovy → JaCoCo, Cobertura C/C++ → gcov, llvm-cov Shell Scripts → kcov, shcov