...

• Click the Open Perspective button in the shortcut bar, choose Other, then choose Code Review in the Select Perspective dialog that opens.
• Choose Window> Open Perspective> Other, then choose Code Review in the Select Perspective dialog that opens.
• Click the Code Review button in the shortcut bar (on the top right of the workbench) if the perspective has been previously opened.

Parasoft Test provides the following provides the following views to facilitate code reviews:

• Quality Tasks view – In Code Review mode, this view displays the code review task tree. It presents two types of tasks: reviewers see "to review" tasks for code revisions they need to review, and authors see "to fix" tasks for responding to reviewer comments. This view should be open by default; to put it in Code Review mode, click the Code Review  or User Code Review button in the view’s toolbar.
  
  
  
  
• Code Review Issue– Allows team members to add and review code comments about the submitted code modifications. This allows the author and reviewer to have a conversation about how to revise a submitted revision. To access this view, choose Parasoft> Show View> Code Review Issue.
• Compare Editor – Highlights the differences between the most recent version of the file and the previous version that was stored under source control. In post-commit mode, it shows the difference between two or more revisions reported to review. It also shows the difference between local changes on desktop and the previous version under source control. The Com-pare Editor will  open when you double-click a specific revision in the code review task tree.

...

Depending  on your import settings, your code review tasks may be imported automatically when you import your quality tasks (as described in Importing Results into the UI).

You can always import your assigned code review tasks into the Quality Tasks view by choosing Parasoft> Import> [desired_import_option] or clicking the Import My Recommended Tasks toolbar button. If you choose to import a custom set of tasks, be sure to enable the Code Review option.

Understanding Task Status Indicators

Depending on how you configure the code review tasks tree, each code review task may be marked with a status indicator, as well as the name of the file, the revision version number, and the time when the latest revision  was committed into the source control. 

The following table describes the various status indicators used:

...

For example, a reviewer with the following task might choose Compare with Previous  

review the code change in the compare editor 

then add an issue in the Code Review Issue area.

...

For instance, the following screenshot shows one possible configuration for Code Review: 

This was configured by a developer trying to group items in a way that lets him to look at things by developer, then by task, and then by location in the code.  That’s how his brain breaks down the information, so that’s how we wanted it presented. More specifically:

...

Another developer who wants to focus on 1) what code reviews to address first and 2) what each code modification was designed to achieve might have the following layout: 

This layout shows the "Task Type" and the "Task or Comment." The "Task Type" sorts the check-ins by date, allowing the reviewer to see which code review to look at first. The "Task or Comment" shows him the intent of the check-in by including the author's comment.

...

To fine-tune what data is displayed in the various tree nodes that you choose to display, you can use the Preferences panel’s Code Review controls to configure which labels are displayed. 

Filters

Additionally, you can filter the content shown by clicking the Filter  button in the Quality Tasks view  

then specifying the desired filter conditions.