iCR for Python User Guides
iCR for Python 3.5
iCR for Python 3.5
  • Table of contents
    • Introduction
    • Overview
    • Authorizing Access to Your Source Code
      • Authenticating GitHub Access with a Cloud-Based VCS Repository Service
        • Authenticating GitHub Access with a Private VCS Repository
      • Authenticating GitLab Access with a Cloud-Based VCS Repository
        • Authenticating GitLab Access with a Private VCS Repository
      • Authenticating Bitbucket Access with a Cloud-Based VCS Repository
    • Using the Navigator
      • Connecting to the Navigator
      • Setting your User Password
      • The Navigator top banner
      • The Analysis Engine status
      • Selecting Your Source Code
        • Using a cloud-based VCS
        • Selecting your branch
        • Using a private VCS
        • Using a local project
        • Limiting the files to be analyzed
      • Integrating with your bug tracking system
        • Integrating with Jira - Define Your Project
        • Integrating with Jira - Authorizing Access for iCR
        • Integrating with Jira - Connecting with iCR
    • Using the Analysis Engine
      • Initiating an analysis
      • Monitoring the analysis
      • Interrupting the analysis
    • Reviewing your results
      • Reviewer summary and filters
      • Filter by Directory pane
      • Filter by Category pane
      • Reviewing a fix
      • Accepting a fix
        • Accepting a fix when integrated with your bug system
      • Rejecting a fix
        • Rejecting a fix when integrated with your bug system
      • Undoing a fix
        • Undoing a fix when integrated with your bug system
      • Rejected fix history
      • Providing feedback
      • Applying the fixes
      • Cases needing manual attention
      • Capturing results for printing or sharing
      • Ending a reviewer session
    • When you are complete
    • Appendix – List of supported fixers
    • Appendix – Example Summary Report
    • Appendix - Sample Bug Listing
Powered by GitBook
On this page
  1. Table of contents

Reviewing your results

PreviousInterrupting the analysisNextReviewer summary and filters

Last updated 1 year ago

Once you have completed an analysis of one of your project branches, you can use the Navigator to begin reviewing the results. Using our earlier example project, following completion of the analysis on the master branch, the Navigator now shows the Review button as being available.

Clicking on the Review button will open a browser tab with a new Reviewer screen. Notice that the top banner from the Navigator screen is also available in the Reviewer, with one exception. The Settings button is gone and replaced by the Home button. This allows you to return to a Navigator from this same tab. This is convenient if you have closed the Navigator tab following the initiation of a Reviewer session.

If you have exhausted your licensed OBLoC capacity, the analysis will still be performed but the Reviewer will not be available following your analysis. Instead, clicking the Review button will display the summary of your analysis. For more information on that, see .

The initial screen displays a summary of all previous analysis sessions (if any). You may have run the ICR Engine more than once. It is helpful to repeat the analysis as you make changes to your code base. Subsequent runs may reveal new issues that were introduced with the changes in the code base.

The sessions will be listed with the most recent at the top of the list and will have the highest Session number. To view the results of any previous analysis, click on its Show Results button.

While you can select the results of any past session, only the most recent will permit the user to make changes. Results from older sessions may only be viewed.

In the example above, we will be reviewing the initial set of results that we just produced so will click on the Show Results button on the right side of the iCR Session: _1_ header.

Example Summary Report