Blog

Visualize the Impact of (automated) Code Reviews

CodeScene integrates with pull requests to provide feedback and detect code quality issues via an automated code review. It’s been a popular integration that helps development teams by serving as a quality gate and early feedback loop. Our new CodeScene release comes with several improvements that support development teams with building high quality software:

  • New virtual code review that includes a detailed description of the issue, motivates why it’s a problem, and provides recommendations on how to fix it.
  • A rich view presenting the pull request delta review.
  • Visualize the trends with respect to impact and actions on pull requests.

We have been using these features internally over the past month, and are excited to make them publicly available in both CodeScene on-premise and CodeScene Cloud!

Pull Requests and Quality Gates: What’s the Impact?

No matter what baseline we start from, we never want our code to become worse. Why make it harder to read, understand, or maintain? No one wants that, but it’s challenging to track given the scale of modern software systems. CodeScene’s pull request integration lets you stay on top of it so that you can prioritize and act upon any negative trends to take your codebase in the desired direction:

View the impact and actions on the automated pull request reviews.

View the impact and actions on the automated pull request reviews.

The statistics show the total number of pull request analyses run by CodeScene, how many issues that were acted detected and then mitigated. Finally the statistics highlight the number of detected issues that were merged as-is, without remediation, to the main branch.

CodeScene also calculates the total code health impact and presents it as monthly trends. These trends let you visualize and communicate improvements, as well as taking actions upon a larger decline:

View the code health impact of the pull request integration.

View the code health impact of the pull request integration.

So what do those trends mean? Well, in the preceding example, we see that Codebase A took on a significant amount of technical debt during November. This should be the basis of a conversation, and something the whole team wants to be aware of. A recommended action in this case could be to plan goals to manage the growing tech debt.

As a contrast, Codebase B shows a positive trend where smaller code improvements are delivered continuously. That’s a nice place to be.

Automated Code Review

You can of course dig into the details of each reviewed PR, and we developers get a summary of the automated review as a PR comment. However, we’re limited to what we can present using safe markdown on GitHub/BitBucket/GitLab/Azure comments. Hence, the automated PR comment now includes a link to a richer presentation inside CodeScene itself:

Get a detailed, automated code review on each Pull Request

Get a detailed, automated code review on each Pull Request.

The virtual code review is of course also available on any file in your codebase via the CodeScene UI.

We hope you enjoy these new features – we know that we do – and as always we are looking forward to your feedback!

New user? Get started in less than a minute!

It is easy to create and set up a free account or a paid plan for larger projects, and try out CodeScene. It is free for all open source repositories and (very) affordable for closed source projects.

Start with the following 1-minute video that explains behavioral code analysis – the next generation of code analysis:

What is Behavioral Code Analysis? Learn about CodeScene.