iCR for Java User Guides
iCR for Java 3.5
iCR for Java 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

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 Baritone project.

Summary: Project Name: baritone

*************************Summary of the Analysis*************************

Start Time: 2022-01-25 23:36:04 PST
End Time: 2022-01-25 23:40:18 PST

Total Runtime: 00:04:14
Ended?: true
Total Java Files: 313
Total Test Files: 6
Total LoC: 21290
Total Exceptions/Errors generated: 1
Total Unique Exceptions/Errors generated: 1
Total Large Calculation Issue generated: 0
Total Long Calculation generated: 0




*************************Details of the Analysis*************************

Parsing Phase: 
   Parsing phase runtime: 00:00:13
   Number of exceptions/errors thrown during file parsing: 0
   Number of unique exceptions/errors thrown during file parsing: 0

Learning Code Structure Phase: 
   Learning Code Structure phase stage-1 runtime: 00:00:07
   Learning Code Structure phase stage-2 runtime: 00:00:14
   Number of exceptions/errors thrown during creating learning code structure stage-1: 0
   Number of unique exceptions/errors thrown during creating learning code structure stage-1: 0
   Number of exceptions/errors thrown during creating learning code structure stage-2: 0
   Number of unique exceptions/errors thrown during creating learning code structure stage-2: 0

   root methods size: 259
   call graph size: 5288


Learning Semantic Phase: 
   Learning Semantic phase runtime: 00:03:08
   Number of points to clusters: 1526


   Points-to-analysis time: 185.0s
   Number of exceptions/errors thrown during Points To: 1
   Number of unique exceptions/errors thrown during Points To: 1

Fixing Phase: 
   Fixing phase runtime: 00:00:32
   Number of exceptions/errors thrown during Fixing: 0
   Number of unique exceptions/errors thrown during Fixing: 0





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

Total Fixes: 25
Object Visibility: 16
  Encapsulation Problem: 16
Null Pointer Issues: 4
  Null Dereference Check: 4
Improper Method Call: 1
  Call Super Method: 1
Inappropiate Logic: 1
  Fix Equality Check: 1
Injection: 1
  Prevent Path Manipulation: 1
Sensitive Data Exposure: 1
  Weak Library Usage: 1
Weak Cryptography Issues: 1
  Use Strong Hash Function: 1
License Key : ABCD-EF12-GH34-56IJ