Setting the scope of your analysis

There may be times when you may want to limit the scope of iCR's analysis. For example, you may find that analyzing the source code for test cases may not be worth the effort. So there is a feature to limit the scope of your analysis results.

Use the Settings menu to select the Define Scope option. This will cause the Navigator to display all of your currently cloned source repositories. Click on the repostiory where you wish to limit the scope of the analysis. In our example, we are using the django repository. Clicking on that presents you with all of the available branches for that repository.

Select the branch for which you wish to define the scope. We will use the main branch for our example. Clicking on the main branch displays the file hierarchy for that branch. If you had previously defined a scope, your previous selections will be shown with the boxes already marked. If not, or if you want to change your selection, click on the boxes adjacent to the directories or files that you want EXCLUDED from the analysis. All other files will be included.

NOTE: If you select a directory for exclusion all files below that directory in the file hierarchy will be excluded.

Once your selections are made, click on Apply to set your choices. Analyses performed following this setting will result in bugs not being detected nor fixes presented for potential issues within that portion of your source.

You may follow the example in the video below to see how these steps are performed. In our example, we choose to exclude all of the tests and docs source code, as well as the build support folders.