Unified Language User Guides
Test Drive iCR 4.0
Test Drive iCR 4.0
  • Table of contents
    • Introduction
    • Overview
    • Using the Navigator
      • Connecting to the Navigator
      • The Navigator top banner
      • The Analysis Engine status
      • Selecting Your Source Code
        • Using GitHub Projects
        • Selecting your branch
        • Limiting the files to be analyzed
    • Using the Analysis Engine
      • Initiating an analysis
      • Monitoring the analysis
      • Interrupting the analysis
    • Reviewing your results
    • When you are complete
    • Appendix – Language Specific Fixer Lists
    • Appendix – Example Summary Report
    • Appendix - Sample Bug Listing
Powered by GitBook
On this page
  1. Table of contents

Using the Analysis Engine

The Analysis Engine works on your source code by focusing only on executable lines of code. It does process some of the comments but the Analysis Engine does not count blank lines or most comments in its OpenRefactory Bundled Lines of Code (OBLoC) count. You can use the cloc Linux command to get an estimate of how many executable lines of code are in your project.

PreviousLimiting the files to be analyzedNextInitiating an analysis

Last updated 1 year ago