# Running with coverage

> For the complete documentation index, see [llms.txt](https://www.jetbrains.com/help/go/2026.3/llms.txt).

GoLand provides a dedicated action for running tests and applications with the code coverage measurement. The code coverage data is processed according to the option selected on the [Coverage](coverage-settings.html) page   of the Settings dialog (`Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `Ctrl+Comma` (VSCode), `⌘ Comma` (VSCode (macOS))).

Procedure: Run tests or an application with code coverage

1. Do one of the following:

* Open the desired file in the editor, and choose `Run <name> with Coverage` from the context menu. When running tests with coverage, note that you can run the entire test file or an individual test function, depending on the caret location.

* Open the desired file in the Project tool window and choose `Run <name> with Coverage` from the context menu. You can also select a directory with test files and choose the corresponding command from the context menu to run several tests with coverage.

* Select the desired run/debug configuration, and then from the main menu choose `Run | Run <run/debug configuration name> with coverage`.

* On the main toolbar, click the `More Actions | Run <run/debug configuration name> with Coverage`. This will launch the selected run/debug configuration.

2. If the Show options before applying coverage to the editor checkbox has been selected in Settings `Ctrl+Alt+S` (Windows), `⌘ Comma` (macOS), `⌘ Comma` (IntelliJ IDEA Classic (macOS)), `⌘ Comma` (macOS System Shortcuts), `Ctrl+Alt+S` (XWin), `Ctrl+Alt+S` (GNOME), `Ctrl+Alt+S` (KDE), `Ctrl+Alt+S` (Emacs), `Ctrl+Alt+S` (Sublime Text), `⌘ Comma` (Sublime Text (macOS)), `Ctrl+Comma` (VSCode), `⌘ Comma` (VSCode (macOS)) `| Build, Execution, Deployment |` [Coverage](coverage-settings.html), a dialog appears where you can choose whether you want to replace the active coverage suites, add the collected data to the active suites, or not apply coverage data. You can also opt to skip this dialog in the future. In case any other option has been selected, the respective action will be performed silently.

3. [Explore the collected coverage data](switching-between-code-coverage-suites.html) in the [Coverage Tool Window](coverage-tool-window.html).

![Run a test with code coverage](https://resources.jetbrains.com/help/img/idea/2026.3/go_running_with_coverage.png)

Procedure: Hide coverage results

* To hide coverage results, you can do the following:

* Close a tab with coverage statistics in the Coverage tool window.

* Click a coverage highlighting in a gutter and select Hide coverage.

[Video](https://resources.jetbrains.com/help/img/idea/2026.3/go_hide_coverage_results.mp4)

## See also

### Procedures

[Run/debug configurations](run-debug-configuration.html)  [Managing code coverage suites](switching-between-code-coverage-suites.html)

### Reference

[Coverage](coverage-settings.html)

