Pytest

Alt+Insert

Create a run/debug configuration.

Alt+Delete

Delete the selected run/debug configuration. Note that you cannot delete default configurations.

Ctrl+D

Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.

The button is displayed only when you select a temporary configuration. Click this button to save a temporary configuration as permanent.

Move into new folder / Create new folder. You can group run/debug configurations by placing them into folders.

To create a folder, select the configurations within a category, click , and specify the folder name. If only a category is in focus, an empty folder is created.

Then, to move a configuration into a folder, between the folders or out of a folder, use drag or and buttons.

To remove grouping, select a folder and click .

Click this button to sort configurations in the alphabetical order.

Name

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

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 CLion stores run configuration settings in .idea/workspace.xml.

Python Interpreter

Select one of the pre-configured Python interpreters.

Target: script/module/custom

Select the target from the drop-down:

• script: a path to a Python file.

• module: a Python module name and a test class instance.

• custom: an arbitrary combination of paths, modules, and test class instances.

Depending on the selected target type, you can specify the following values:

• Path to the test file, for example, /Users/jetbrains/Car/my_tests/test_car.py. You can type in the path or click the button to locate the file in the project structure.

• Name of the module in your project, for example, my_tests. You can type in the module name, search the target module by its name, or locate it in the project structure.

• Custom combination of modules, scripts, classes, and methods, for example, my_tests.test_car.TestCar.test_brake, where:

  • my_tests: the package name

  • test_car: the module name

  • TestCar: the class instance in test_car

  • test_brake: the method in the TestCar class

Additional Arguments

In this text field, specify the additional framework-specific arguments to be passed to the test as-is, for example:

Keywords

An expression to match on the test names. See examples on docs.pytest.org.

Environment variables

Click the browse button, or press Shift+Enter to specify the desired set of environment variables in the Environment Variables dialog. To create a new variable, click , and type the desired name and value.

Docker container settings

Click to open the dialog and specify the following settings:

Options

• Disable networking: select this checkbox to have the networking disabled. This corresponds to --net="none", which means that inside a container the external network resources are not available.

• Network mode: corresponds to the other values of the option --net.

  • bridge is the default value. An IP address will be allocated for container on the bridge’s network and traffic will be routed through this bridge to the container.

    Containers can communicate via their IP addresses by default. To communicate by name, they must be linked.

  • host: use the host's network stack inside the container.

  • container:<name|id>: use the network stack of another container, specified via its name or id.

  For more information, refer to the Network settings documentation.

• Links: Use this section to link the container to be created with the other containers. This is applicable to Network mode = bridge and corresponds to the --link option.

• Publish all ports: Expose all container ports to the host. This corresponds to the option --publish-all.

• Port bindings: Specify the list of port bindings. Similar to using the -p option with docker run.

• Extra hosts: This corresponds to the --add-host option. For more information, refer to Managing /etc/hosts.

• Volume bindings: Use this field to specify the bindings between the special folders-volumes and the folders of the computer, where the Docker daemon runs. This corresponds to the -v option. For more information, refer to Managing data in containers.

• Environment variables: Use this field to specify the list of environment variables and their values. This corresponds to the -e option. For more information, refer to ENV (environment variables).

Click to expand the tables. Click , , or to make up the lists.