iCR for Python User Guides
iCR for Python 3.0.2
iCR for Python 3.0.2
  • Table of contents
    • Introduction
    • Overview
    • Getting Started
      • Installing iCR for Python
      • Managing your service
        • Opening Ports
      • 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
          • Authenticating Bitbucket Access with a Private VCS Repository
          • Setting Bitbucket Server Credentials in the Navigator
    • Using the Navigator
      • Connecting to the Navigator
      • Setting your private passphrase
      • 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
        • Setting the scope of your analysis
      • 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

Appendix – Example Summary Report

PreviousWhen you are completeNextAppendix - Sample Bug Listing

Last updated 1 year ago

When an analysis completes, a prompt is displayed requesting that you send OpenRefactory a brief summary of your analysis. The data we send does not include any information about your source code.

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, the Review button will give you a window which will display the summary results.

If you wish to retain the contents of the summary to share with others, you can click on the Save as pdf button to save a copy.

Depending upon your browser, the Save as pdf option may behave differently. For example, Firefox gives you the choice to view the PDF in a new tab or save as a file. In the case of Chrome, it is a bit clumsy to save as a file as you can only do that if you have your Chrome preference set for that. To do that using Chrome select

To show you what we include in our summary, below is an example from an analysis performed on the Open Source example used in the Guide, the django project.

Summary: Project Name: django
*************************Summary of the Console***********************

Start Time:
End Time: 2021-09-29 02:53:50 PST

Parsing Phase:
CG Phase:
Points To Phase:
Fixing Phase:
        Fixing phase runtime: 00:03:32
        Number of exceptions/errors thrown during Fixing: 0
        Number of unique exceptions/errors thrown during Fixing: 0


-----------------------------All Exceptions---------------------------
-----------------------------------------------------------------------


Parsing Phase Exceptions:
-----------------------------------------------------------------------
-----------------------------------------------------------------------



CallGraph Phase Stage-1 Exceptions:
-----------------------------------------------------------------------
-----------------------------------------------------------------------



CallGraph Phase Stage-2 Exceptions:
-----------------------------------------------------------------------
-----------------------------------------------------------------------



PointsTo Phase Exceptions:
-----------------------------------------------------------------------
-----------------------------------------------------------------------



Fixing Phase Exceptions:
-----------------------------------------------------------------------
-----------------------------------------------------------------------



*****************Summary of the Results************

Total Fixes: 32
PyUSA: 15
        PyUSA-11: 14
        PyUSA-9: 1
PyARP: 17
        PyARP-2: 17
License Key: ABCD-EF12-GH34-56IJ