Unit tests and integration tests let you validate that your application behaves correctly under different circumstances. They also ensure that you didn’t introduce any regression when adding or refactoring code. But how can you verify that your tests are valid? Using test code coverage! CABL will let you verify that all your new code is really tested.
Duplication is one of the root problems when working with code. Every time a developer copies and pastes code from another location, all code smells, bugs and vulnerabilities are duplicated, making it even harder to decrease the technical debt. CABL and SonarQube can identify duplicated code, so that developers can refactor the code into common procedures and classes instead of copy-pasting them.
Compilation warnings are often overlooked because they tend to get lost in compilation reports which are buried in your continuous integration server logs. But lots of warnings can be really useful, such as dead code or functions not returning any value. As usual with SonarQube, you’ll be able to focus on compilation warnings introduced in new code, so your developers will be able to stay focused on what they’re really working on.