Coverage
for Windows and Linux
for macOS
Ctrl+Alt+S 
Use this page to configure how coverage data is collected and processed.
When new coverage is gathered
These options control how collected coverage data is processed.
Item | Description |
|---|---|
Show options before applying coverage to the editor | Show the Code Coverage dialog every time you launch a new run configuration with code coverage. The coverage options dialog is displayed when different coverage data has been produced. |
Do not apply collected coverage | Discard new code coverage results. |
Replace active suites with the new one | Discard active suites and use the new one every time you launch a new run configuration with code coverage. |
Add to active suites | Append new code coverage suite to the active suites every time you launch a new run configuration with code coverage. |
Activate coverage view | Show the Coverage tool window when an application or test is run with coverage. |
Java coverage
These options control which Java code elements should be excluded from coverage statistics.
Item | Description |
|---|---|
Ignore implicit constructors | Exclude implicitly declared default constructors from coverage statistics. Default constructors that are declared explicitly will remain included. |
Ignore empty private constructors of utility classes | Exclude from coverage statistics empty private constructors in classes where all other methods are static. |
Python coverage
These options are available only if the Python plugin is enabled.
Item | Description |
|---|---|
Use bundled coverage.py | Use the bundled |
Branch coverage | Enable branch coverage in the coverage.py script. Thus additional information to the pure line coverage reports is added, marking the coverage of lines with conditional statements as incomplete in case one or more branches haven’t been executed.  For more information, see this page. |