Run/debug configurations
GoLand uses run/debug configurations to run, debug, and test your code. Each configuration is a named set of startup properties that define what to execute and what parameters and environment should be used.
There are two types of run/debug configurations:
Temporary — created every time you run or debug functions or tests.
Permanent — created explicitly from a template or by saving a temporary configuration. Permanent configurations remain as part of your project until you remove them.
So whenever you run/debug or test your code, GoLand either uses an existing permanent run/debug configuration or creates a new temporary one.
Permanent configurations have opaque icons while the icons of temporary configurations are semi-transparent.
The maximum number of temporary configurations is 5. The older ones are automatically deleted when new ones are added. If necessary, you can increase this limit in
.Create permanent run/debug configurations
GoLand provides the following ways to create a permanent run/debug configuration:
Create from a template or copy an existing configuration.
Save a temporary configuration as permanent
Select a temporary configuration in the run/debug configuration switcher, click / , and select Save Configuration.
Alternatively, select a temporary configuration in the Run/debug configurations dialog and click on the toolbar.
GoLand provides run/debug configuration templates for different languages, tools, and frameworks. The list of available templates varies depending on the installed and enabled plugins.
Create a run/debug configuration from a template
Go to
. Alternatively, press Alt+Shift+F10, then 0.In the Run/Debug Configuration dialog, click on the toolbar or press Alt+Insert. The list shows the run/debug configuration templates. Select Go build.
Specify the run/debug configuration name in the Name field. This name will be shown in the list of the available run/debug configurations.
On the Configuration tab, you can set the following options:
In the Before launch section, define whether you want to perform any specific actions before launching the application, for example, launch an external tool or another build configuration before run. To skip the build stage, remove Build from the Before launch list .
You can either run the configuration right away, or save the configuration to run it later.
Click OK to save the run configuration for later and close the dialog.
To run the configuration right away, click Run.
List of fields in Go Build configuration
Name | Description |
---|---|
Run kind | Building scope for your application. File and Package scopes work similarly in tests and compilation/running configurations (in terms of the scope they cover).
|
Package path | Full import path of the package that you want to compile (for example, You can press Control+Space to see a list of available packages. |
Output directory | Path to a directory where you want to output the executable file. |
Run after build | Execute the application after the build. |
Redirect input from | File to read the input from. |
Working directory | Directory that is used for the built application. If you have any code that creates relative files or directories, they will be relative to this directory. |
Environment | Environment variables for your application. To edit environment variables, click the Browse button at the end of the field. In the Environment Variables dialog, click the Add button and add the environment variables that you need. |
Go tool arguments | Arguments for the go tool (for example, |
Use all custom build tags | All tags that are applied during the build. Tags are listed in settings Control+Alt+S under . |
Program arguments | Arguments for the built application. Also, you can use macros in this field. |
Run with sudo | Run the application with elevated privileges. |
Module | Name of the current module. |
Before launch | Add tasks that you want to launch before the launch of the selected run/debug configuration. To add a task click the Add button Alt+Insert and select the tool that you want to add. |
Store as project file | Enable this option to save your configuration as a project file and share it with team members through VCS. |
List of fields in Go Test configurations
Name | Description |
---|---|
Test framework | Select the package that you want to use to run tests.
|
Test kind | Select the scope from which you want to run tests:
|
Pattern | Regular expression that defines what tests to run. GoLand will run only those tests, examples, and fuzz tests that match the regular expression. For tests, the regular expression is split by unbracketed slash ( |
Working directory | Directory that is used for the built application. If you have any code that creates relative files or directories, they will be relative to this directory. |
Output directory | Directory that stores your test results if any. |
Run after build | Execute a test after the build. |
Redirect input from | Path to the file that will to take program input instead of the console. |
Working directory | Directory that is used for the built application. If you have any code that creates relative files or directories, they will be relative to this directory. |
Environment | : environment variables that you need to run the test. To edit environment variables, click the Browse button at the end of the field. In the Environment Variables dialog, click the Add button and add the environment variables that you need. |
Go tool arguments | Arguments for the go tool (for example, |
Use all custom build tags | All tags that are applied during the build. Tags are listed in settings Control+Alt+S under . |
Program arguments | Arguments for the test. |
Run with sudo | Grant sudo privileges to the test. |
Before launch: Activate tool window | Add tasks that you want to launch before the launch of the selected run/debug configuration. To add a task, click the Add button Alt+Insert and select the tool that you want to add. |
Share run/debug configurations
If you are working in a team, you might want to share your run/debug configurations so that your teammates could run the application using the same configuration or enable them to remotely attach to the process you are running.
For these purposes, GoLand provides a mechanism to store your run/debug configurations as project files and share them through VCS. The same mechanism can also be used when you want to send your configuration as a file to someone else. This saves a lot of time as run/debug configurations sometimes get sophisticated, and keeping them in sync manually would be tedious and error-prone.
Go to
. Alternatively, press Alt+Shift+F10, then 0.Select the run/debug configuration you want to share, enable the Store as project file option, and specify the location where the configuration file will be stored.
If compatibility with GoLand 2019.3 and earlier is required, store the file in the default location.
(Optional) If the .idea directory is added to VCS ignored files, the .idea/runConfigurations subfolder will be ignored, too. If you use Git for your project, you can share .idea/runConfigurations only and leave .idea ignored by modifying .gitignore as follows:
/.idea/* !/.idea/runConfigurations
Run/debug configuration templates
All run/debug configurations are based on templates, which implement the startup logic, define the list of parameters and their default values. The list of available templates is predefined in the installation and can only be extended via plugins. However, you can edit default parameter values in each template to streamline the setup of new run/debug configurations.
Configure the default values for a template
Go to
. Alternatively, press Alt+Shift+F10, then 0.In the left-hand pane of the run/debug configuration dialog, click Edit configuration templates….
In the Run/Debug Configuration Templates dialog that opens, select a configuration type.
Specify the desired default parameters and click OK to save the template.
Run/debug configuration folders
When there are many run/debug configurations of the same type, you can group them in folders, so they become easier to distinguish visually.
Once grouped, the run/debug configurations appear in the list under the corresponding folders.
Create a folder for run/debug configurations
Go to
. Alternatively, press Alt+Shift+F10, then 0.In the Run/Debug Configurations dialog, select a configuration type and click on the toolbar. A new empty folder for the selected type is created.
Specify the folder name in the text field to the right or accept the default name.
Select the desired run/debug configurations and move them under the target folder.
Apply the changes. If a folder is empty, it will not be saved.
When you no longer need a folder, you can delete it Delete. The run/debug configurations grouped under this folder will be moved under the root of the corresponding run/debug configuration type.