Go Test

Create: Run | Edit Configurations | | Go Test

With the Go Test configuration, you can run and debug Go tests. For more information about running tests, refer to the following topics:

List of fields in Go Test configurations

Name	Description
Test framework	Select the test framework to use. gotest: run standard Go tests. For more information about `go test`, refer to Package testing. gocheck: run tests with the gocheck framework. gobench: run benchmarks. For more information, refer to Package testing: Benchmarks. go test -fuzz: run fuzz tests. Fuzzing sends random or unexpected input to your code to find problems. For more information, refer to Go Fuzzing. Use Run to start fuzzing. The Debug action is unavailable for the go test -fuzz framework.
Test kind	Select the scope from which you want to run tests: Directory: run tests in the selected directory and its subdirectories. Specify the directory in the Directory field. To debug tests, select Package instead. Package: run tests in a package. In the Package path field, enter the package import path, for example, `example.com/myapp/calc`. File: run tests from the selected files. In the Files field, enter file paths separated by `\|`, for example, `/work/myapp/calc.go\|/work/myapp/calc_test.go`. Select files from the same directory. At least one file needs to support the selected test framework.
Pattern	This field is available for Directory and Package scopes. For File scope, GoLand generates the pattern from the test functions in the selected files when no pattern is set. Enter a regular expression to select the tests to run. For tests with subtests, separate the expressions with `/`. The first expression matches the test name, and each following expression matches a subtest name at the next level. For example, to run the `add_positive_and_negative` subtest of `TestAdd`, enter `^\QTestAdd\E$/^\Qadd_positive_and_negative\E$`. To generate the pattern, run a subtest or a set of tests from the gutter. You can then edit the pattern in the generated configuration.
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 for the compiled test executable when you use File or Package scope.
Build on remote target	This checkbox appears when you select a non-local run target. It is cleared by default. Select it to copy the source files to the target and build there. When you select it, GoLand hides the Output directory field. Clear it to build locally and copy the executable to the target. If the selected Go SDK is located in WSL, GoLand builds on the run target even when this checkbox is cleared. For more information, refer to Run on a target.
Redirect input from	Path to the file to use as standard input instead of the console.
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, `-tags`).
Use all custom build tags	Select this checkbox to add the tags from the Custom tags field under Go \| Build Tags to the build command. If Go tool arguments already contains `-tags`, the command uses those tags instead. If neither Go tool arguments nor this checkbox supplies `-tags`, GoLand can select tags from `//go:build` and `// +build` constraints in the test files. This applies to File scope and to Package scope when GoLand can identify the selected test functions.
Program arguments	Arguments for the test.
Run with sudo	Run the tests with elevated privileges. This option is available for local configurations when the operating system supports process elevation.
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.

Common settings

When you edit a run configuration (but not a run configuration template), you can specify the following options:

Item	Description
Name	Specify a name for the run configuration to quickly identify it among others when editing or running.
Allow multiple instances	Allow running multiple instances of this run configuration in parallel. By default, it is disabled, and when you start this configuration while another instance is still running, GoLand suggests stopping the running instance and starting another one. This is helpful when a run configuration consumes a lot of resources and there is no good reason to run multiple instances.
Store as project file	Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project. By default, it is disabled, and GoLand stores run configuration settings in .idea/workspace.xml.

Item

Description

Name

Specify a name for the run configuration to quickly identify it among others when editing or running.

Allow multiple instances

Allow running multiple instances of this run configuration in parallel.

By default, it is disabled, and when you start this configuration while another instance is still running, GoLand suggests stopping the running instance and starting another one. This is helpful when a run configuration consumes a lot of resources and there is no good reason to run multiple instances.

Store as project file

Save the file with the run configuration settings to share it with other team members. The default location is .idea/runConfigurations. However, if you do not want to share the .idea directory, you can save the configuration to any other directory within the project.

By default, it is disabled, and GoLand stores run configuration settings in .idea/workspace.xml.

Before launch

In this area, you can specify tasks to be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.

Item	Shortcut	Description
	`Alt+Insert`	Click this icon to add one of the following available tasks: Launch Web Browser: select this option to have a browser started. In the dialog that opens, select the type of the browser and provide the start URL. Also, specify if you want the browser to be launched with the JavaScript debugger. Run External tool: select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in GoLand yet, add its definition. Run Another Configuration: select to execute another run/debug configuration and wait until it finishes before starting the current configuration. If you want to run several configurations in parallel, use a compound run/debug configuration. Run File Watchers: select this option to have GoLand apply all the currently active File Watchers. Run Remote External Tool: adds a remote SSH external tool. Run Grunt task: select this option to run a Grunt task. In the Grunt task dialog that opens, specify the Gruntfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Grunt tool. Specify the location of the Node.js runtime, the parameters to pass to it, and the path to the grunt-cli package. Run gulp task: select this option to run a Gulp task. In the Gulp task dialog that opens, specify the Gulpfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Gulp tool. Specify the location of the Node.js runtime, the parameters to pass to it, and the path to the gulp package. Run npm script: select this option to execute an npm script. In the NPM Script dialog that opens, specify the npm run/debug configuration settings. Compile TypeScript: select to run the built-in TypeScript compiler and thus make sure that all the changes you made to your TypeScript code are reflected in the generated JavaScript files. In the TypeScript Compile Settings dialog that opens, select or clear the Check errors checkbox to configure the behaviour of the compiler in case any errors are detected: If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start. If the Check errors checkbox is cleared, the compiler will show all the detected errors but the run configuration still will be launched. Run Go Command: select to run a Go command before running your program. For example, you can run `go generate` to generate source code before compilation. In the Edit Go Command Task dialog, you can use auto-completion. Auto-completion supports the following commands `generate`, `vet`, `test -i`. You can use your own commands. Disconnect Data Source: select this option if you want to disrupt the connection to a data source before the run/debug configuration is run.
	`Alt+Delete`	Click this icon to remove the selected task from the list.
	`Enter`	Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
	`Alt+Up` `Alt+Down`	Click these icons to move the selected task one line up or down in the list. The tasks are performed in the order that they appear in the list.
Show this page		Select this checkbox to show the run/debug configuration settings prior to actually starting the run/debug configuration.
Activate tool window		By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration. Otherwise, if the checkbox is cleared, the tool window is hidden. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing `Alt+4` or `Alt+5`.
Focus tool window		Select this checkbox to automatically move focus to the Run or the Debug tool window when you start the run/debug configuration.

Logs

The following options are related to logging the execution of this configuration. For more information, refer to Setting log options.

Item	Description
Specify logs to be shown in the console	Specify which log files to display while running the application. Click to add a new log. In the Edit Log Files Aliases dialog, configure the following: Alias: The name of the tab where the log will be displayed. Log File Location: Specify the path to the log file or an Ant pattern. If several files of a rolling log match the pattern, GoLand will display the most recent one. Show all files coverable by pattern: Show all logs that match the pattern. For logs in the table, you can configure the following options: Is Active: Display the specified log file. Skip Content: Do not display old log messages from previous runs.
Save console output to file	Save the console output to the specified location. Type the path manually or click the browse button and point to the desired location in the dialog that opens.
Show console when a message is printed to stdout	Activate the console when the application writes to the standard output stream.
Show console when a message is printed to stderr	Activate the console when the application writes to the standard error stream.

17 September 2026