Run inspections

1. In the main menu, go to Code | Inspect Code.

2. Select the scope of files that you want to analyze.

   Click the icon to configure a new scope.

3. Select the inspection profile that you want to apply.

   To create a new profile or modify one of the existing profiles, click Configure.

4. Click Analyze to start the analysis.

Running a single inspection is useful in case you want to track a specific problem. If you find a warning in a file, you can inspect your entire project, or the necessary scope of files, to ensure that there are no more such warnings in your code base.

1. Press CtrlAltShift0I or go to Code | Analyze Code | Run Inspection by Name in the main menu.

2. Type the inspection name in the popup. Use CamelHumps to match camel case words and white spaces with initial letters of the words. The suggestion list will show you inspections that match your search request.

   If you are not sure that you are selecting the correct inspection, you can view its description. To do so, select an inspection in the popup and press Ctrl0Q.

3. Double-click the necessary inspection.

4. In the dialog that opens, select the scope of files that you want to analyze.

   The File mask(s) option helps you narrow down the number of files that will be inspected.

   Select the checkbox and specify a pattern of characters and wildcards that matches the names of files you want to analyze. Use a comma to separate multiple file masks.

5. Some inspections might have additional options that you will be prompted to configure.

   These settings will only be applied to this run and will not affect this inspection's configuration in your current profile.

   The IDE will show you the inspection results in the dedicated tool window tool window. There you can examine and fix detected problems.

1. Press Alt00 to open the Commit tool window and click Show Commit Options .

2. In the Commit Checks area, select the Analyze code checkbox.

3. Click Choose profile and select the required inspection profile from which the IDE will run inspections.

   

4. Click Commit.

   IntelliJ IDEA analyzes the code from the modified files by running inspections from the selected profile.

   If any errors or warnings are detected, you will see a notification.

   

5. In the notification, click Review code analysis to see the list of the detected problems in the Messages tool window. Click Ignore to commit your changes without fixing the detected problems.

1. In the main menu, go to Tools | Qodana | Try Code Analysis with Qodana.

2. Select where you want to run inspections: locally or on your CI/CD server.

   To run inspections on the server, you need to set up Qodana on your CI first.

3. The Qodana configuration file opens. In this file, you can specify a Qodana inspection profile, enable or disable specific inspections, and specify a list of plugins that should be installed before the analysis.

   Click Run.

Once the analysis is finished, the report will be displayed in the Problems tool window on the Server-Side Analysis tab. You can work with the results locally or send them to Qodana Cloud.

The reports of all local runs of Qodana analysis are saved and available from the main menu: Tools | Qodana | [report name]. The currently opened report has a checkmark next to it, you can click it to close the report.

1. In the Settings dialog (CtrlAlt0S) , select Editor | Inspections.

2. Select any inspection from the list.

3. From the In All Scopes list, select Edit Scopes Order.

4. Select the necessary scope, and use and to move it up and down the list.

   

5. If needed, create a new scope. To do so, click (Edit Scopes), specify scope settings, and select the files and folders that you want to include in it.