Sky Image

Automate Your Code Reviews with Static Code Analysis

One of the most common question I have to answer software engineers when talking about Codacy is “Automated Code Reviews? Really? How can this work?”.

(Peer) Code Reviews established itself as one the common best practice in modern software engineering workflows. But if you ask engineers they will tell you that most of the time code reviews are about enforcing best practices, code style, and common security issues. 100% of those issues can be found by static analysis and linting tools. In this article, we will see how you can use static analysis to save up to 70% in code review time. (more…)

Read More

Blog Post Background Blue

What your mother didn’t tell you about Code Coverage

What is Code Coverage

Code Coverage is a measure that describes the degree to which code has been tested. The higher the Code Coverage of a project, the more thoroughly tested it has been, and thus the chance of it containing bugs is (usually) smaller.

How it works

There are several ways that Code Coverage can be implemented (and usually you won’t have to know how it really works unless you’re creating a coverage tool).
One of the possibilities is to implement checks throughout the code, run the test suite, and then analysing how many of those checks were actually run.


Read More

pablo (2)

Why you’re not merging your pull requests and what to do about it

Or how to avoid merge limbo
With few exceptions, every developer I meet has mentioned frustration in managing long-lived pull requests.
Long-lived pull requests are pull requests that for some reason are stuck in a backlog without being approved and are in a merge limbo.
Pull requests can enter this limbo state for many reasons.

I’ll describe a few of these below and propose a few solutions.


Read More