code review

Evaluating Developer’s Performance in Code Review Process

Summary: This article describes how to estimate the coverage with code review of code written by individual developers.

The article builds upon Estimating Coverage of Project’s Source Code with Code Review. As from version 2.6, Review Assistant, Devart’s code review tool, provides the new Code Coverage report. Developed in response to numerous requests from our customers, the report serves for a better quality control over the code review process. Within the context of this article, we would like to show how to:

  • Evaluate team performance in the code review process
  • Evaluate individual developer’s performance (more…)

Estimating Coverage of Project’s Source Code with Code Review

Summary: This article describes how to estimate the project’s source code coverage with code review. The article also gives an outline of how to make the most from Review Assistant’s Code Coverage report.

As from version 2.6, Review Assistant, Devart’s code review tool, provides the new Code Coverage report. Developed in response to numerous requests from our customers, the report serves for a better quality control over the code review process. Within the context of this article, we would like to show how to effectively use the tool. In particular, we will elaborate on how to:

  • Exclude excessive data from a report with filtering
  • Group report data
  • Interpret report results

(more…)

Creating TFS Custom Check-in Policy – Part 2

This is the second article of the two-part series that explains implementation of the TFS custom check-in policy for pre-commit code review. We developed this policy for Review Assistant – our code review tool.

In the first article we explained what is a check-in policy and what is the implementation procedure. This article shows nuts and bolts behind our implementation of a check-in policy.

In this article, we shall discuss:

  • The algorithm of our Pre-Commit Code Review policy;
  • Main problems of implementing the algorithm;
  • Restrictions of the policy implementation.

(more…)

Agile Code Review Process with Review Assistant

Summary: This article describes a scenario of Review Assistant usage in agile development process. The peculiarity of this scenario is that every team member is allowed to join a code review.

Some time ago we received the following question through our technical support:

Hi guys!
Our company is currently evaluating Review Assistant, we are using ‘Simple review workflow’ in our project.
The issue is there is no way to create review without assigning a reviewer to it. This doesn’t allow us to use agile process, when anyone who is available can join a review.
Is there any way to create review in current version?

(more…)

Tweak for ‘Simple Review Workflow’

Summary: In Review Assistant 2.0 we have modified the simple review workflow. Now it is possible to add a code-related comment and accept author’s changes, and at the same time leave the review open.

 

This is the fifth article in the series of What’s New in Review Assistant 2.0

How does simple review workflow work?

There are three review roles by default:

  • Author — the person who creates code.
  • Reviewer — the person who inspects code.
  • Moderator — the person who double checks a review and settles disputes.

Here is how it looks like in the application:

(more…)

Iterative Code Review 2.0

Summary: This article describes improvements we have introduced into the iterative code review process — the distinctive Review Assistant feature.

This is the fourth article in the series of What’s New in Review Assistant 2.0

What is iterative code review?

Iterative code review refers to the situation when a single piece of work is reviewed more than once by the same reviewer.
In fact this is a regular case. None of major changes in code will pass without reviewers comments. They find bugs and faults which an author should fix, and then show the code over again.
The Review Assistant documentation contains more detailed description of the iterative code review.
Not all code review tools support repetitive code inspections within a single review. Review Assistant has been providing this feature since the first release. In Review Assistant 2.0 we have significantly improved this process.
(more…)

Reviewing Code from Multiple Repositories in One Review

Summary: This article describes new Review Assistant features, namely: the possibility to work with several repositories within a single review, and also the possibility to add nested repositories into a project.

This is the third article in the series of What’s New in Review Assistant 2.0

While working on a large scale projects it is not uncommon that the source code is stored in more than one repositories. Devart’s own projects are not an exception.

From the very first release of Review Assistant there was the possibility to associate several repositories with a single project. However, while creating a new review there was only the possibility to add files from one repository.
(more…)

Improved Code Review Comments in Review Assistant 2.0

Summary: One of our main missions, while working on the new version of Review Assistant was to improve user experience in general. This article describes how we have solved some UX problems related to the commenting on code.

This is the second article in a series of What’s New in Review Assistant 2.0
(more…)

Code Review Board Re-designed

Summary: In Review Assistant v2.0 we have completely redesigned the Code Review Board window. We have made efforts to make performance more straightforward, and to make the application UI more natural for Visual Studio 2012 and 2013.

This is the first article in a series of What’s New in Review Assistant 2.0

While working on the new version of Review Assistant, we studied UX problems detected earlier. Solutions for many of these problems required application’s interface changes. We had started development of Review Assistant v 1.0 long before Visual Studio 2012 was released. That’s why the UI was more suitable for Visual Studio 2010. To go with the times we have decided to redesign the main window — Code Review Board.

(more…)