Code Review Tool allows team members to review code collaboratively in an easy and efficient manner by removing most of the overhead associated with regular formal code inspections. It provides all the benefits of formal code inspections and requires considerably less effort and time compared to formal code inspections. It supports both formal and lightweight code review processes.
Dashboard provides each user with summary of all open reviews they are associated with. It also lists the summary details most recent 50 reviews which the user was associated with, either as a reviewer or author, to quickly navigate to review details.
Depots simplify creation of post-commit reviews. Depot represents an existing project in a particular kind of version control system. Review authors create and manage multiple depots to access existing source code, which needs to be reviewed, for different products on different version control systems.
Code Review Tool supports creating reviews from Team Foundation Server commits.
Code Review Tool supports creating reviews from Subversion commits.
A review has a single author and one or more reviewers. Author can invite other users in Code Review Tool system as reviewers to review the code changes. A review instance is only visible to its author and reviewers.
Post-commit reviews are reviews made up of changes which have already been committed to version control system. Pre-commit reviews are reviews made up of changes which are present in author’s workspace and are not yet committed to a version control system. You can create reviews from both post-commit and pre-commit changes.
As different versions of source code are added to the review, by selecting multiple changelists, the Code Review Rool automatically consolidates the differences and shows effective difference between the first and latest version of the source code. It also provides the user with an option to view the differences between any two versions of the source code.
A review can contain one or more changelists from a single or multiple depots. A changelist contains one or more files which have been changed and needs to be reviewed.
After creating the review author starts the review process. Once a review is started, it becomes visible to invited reviewers. Email notifications are also sent to invited reviewers with details about the review and link to the review.
You can self review your code by inviting yourself as the reviewer while creating a review for your code.
Viewing differences in the code and managing comments is where users of a review spend most of their time. All the differences between two versions of a source file are shown together in a page. Review details page contains links to all the differences pages for all the source files present in a review.
Viewing differences in the code and managing comments is where users of a review spend most of their time. All the differences between two versions of a source file are shown together in a page. Review details page contains links to all the differences pages for all the source files present in a review.
Multiple difference views, like merged difference view and side by side difference view, allows users to easily understand the differences. Users can easily switch between different views.
Summary difference views allow reviewers to quickly concentrate on the differences between two versions of a source code. Summary difference views minimize the common portions of the source code to a summary line that can be expanded by the user on demand. Summary difference view is particularly useful for scenarios where the files are large but the difference between the two versions is small.
Syntax highlighting highlights different keywords of programming languages in different colors to improve comprehension and readability of the source code. Syntax highlighting supports all different major programming languages and support for a new programming language can be added easily.
Syntax highlighting of JavaScript source files.
Syntax highlighting of XML source files.
Reviewers go through the differences in source code and start discussions on portions of code where they find an issue to inform the author. Starting discussion is very easy and intuitive, reviewers just select a set of lines in source code and select "New Discussion" menu item to enter details about the issue.
The old and newly created discussions are overlaid over source code with a discussion icon on left most column. The users can drill into the details of each discussion by expanding discussion details inline over the source code or by opening a particular discussion details in a separate page. A discussion details page lists details of the discussion and along with the portion of the source code associated with the discussion.
Discussion details expanded inline on source code difference view.
A discussion can be two states - "open" and "closed". Open discussions identify open issues where as closed discussions identify issues which are closed. A reviewer who created the discussion changes the discussion's state to "closed" after verifying the issue was fixed by the author. The user, generally a reviewer, who created the discussion, can alone change the status of a discussion. All users of a review can respond a discussion with their comment.
New discussions and new comments by a reviewer are published to other users of the review only after the reviewer marks his or her status for a review as "completed". This allows the reviewer to start new discussions and add comments to existing discussions and later redact them, if needed, before marking the review as "completed".
Multiple views of discussions allow the review users to easily manage the discussions. Discussions of a review.
Discussions of a file.
All open discussions of a review.
A user can search across reviews, discussions, changelists and file (source code) using a text search string. The search can also be filtered by any of the following four types of objects: Reviews, Discussions, Changelists, File (source code).
Advanced search scenarios are also supported. For e.g. searching for all "open" reviews which have a user named ‘bob’ or searching for all discussions which are "open" etc.
Download trial version of Code Review Tool for installation. Go through Code Review Tool demonstration video.