Review the code with the RTC's own Code review tool

This article describes the Code Review feature (Review) of the IBM Rational Team Concert (RTC). This feature enables the code review process to become more standardized, refine the code submission process, and be more efficient for members of different regions to http://www.aliyun.com/zixun/aggregation/18521.html "> work together, Find potential problems before the code is submitted, fix them as soon as possible, improve the quality of the code, and effectively reduce the number of defects.

The importance of code review

In most cases, reviewers can find problems or potential problems that the developer cannot find themselves, and there will be differences in thinking patterns and points of consideration.

The good reviewers pass the review, not only can you discover the shortcomings of the developers, but also through the developer's code to learn a lot of knowledge to the team, through the review and mutual review, understand the other team members responsible for the task, when necessary to help each other, mutual support, improve project development efficiency, reduce project risk

Code review rules

Logically speaking, is this modification to meet the requirements, whether there are similar places need to modify the readability, whether there is enough explanation to maintain the code specifications in the future, compliance with the company code to maintain code consistency from the code performance, whether there are more effective solutions to achieve Unit test (if necessary), whether the test case can overwrite this modification

RTC Support for code review

As the current mainstream code management tool, the RTC has a good support for the function of code review, such as the use of mail as a code submitter and reviewer communication tools, code review process of the role of the Division of the code to submit the permissions set, etc., this section will specifically describe the RTC The concepts and detailed configuration involved in the code review process.

Support for messages

Throughout the code review process, the message is as a code submitter and other relevant personnel between the important communication tools, such as the code before the review submitted to add changes to the code, the team should receive a corresponding message reminder, users can be configured to enable mail support:

Open the Repository 50x15 interface and connect

Figure 1. Repository Connection Interface

Open the User editing window as shown in Figure 2:

Figure 2. Open my User Editor

Locate the Mail revisit page and configure and save it accordingly, as shown in Figure 3:

Figure 3. Mail Configuration Interface

Division of roles involved in code review