Configuration
| Item | Description |
|---|---|
| 1.2+Target | Specify the target to be executed. If the field is left empty, it means that all the tests in all the applications specified in INSTALLED_APPS will be executed.
Same rules apply to the doctests contained in the test targets. The test label is used as the path to the test method or class to be executed. If there is function with a doctest, or a class with a class-level doctest, you can invoke that test by appending the name of the test method or class to the label. |
| Custom settings | If this check box is selected, Django test will run with the specified custom settings, rather than
with the default ones.
Specify the fully qualified name of the file that contains Django settings. You can either type it manually, in the text field to the right, or click the browse button, and select one in the dialog box that opens. If this check box is not selected, Django test will run with the default settings, defined in the Settings field of the Django Support page. The text field is disabled. |
| 2.7+Options | If this check box is selected, it is possible to specify parameters to be passed to the Django tests.
Type the list of parameters in the text field to the right, prepending parameters with '--' and using spaces
as delimiters. For example:
--noinput --failfast
If this check box is not selected, the text field is disabled. |
| Project | Click this drop-down list to select the desired project. |
| Environment variable | This field shows the list of environment variables.
If the list contains several variables, they are delimited with semicolons. To fill in the list, click the browse button, or press Shift+EnterShift+Enter and specify the desired set of environment variables in the Environment Variables dialog box. To create a new variable, click  , and type the desired name and value. |
| Python Interpreter | Select one of the pre-configured Python interpreters from the drop-down list. |
| Interpreter options | In this field, specify the string to be passed to the interpreter. If necessary,
click  , and type the string in the editor. |
| Working directory | Specify a directory to be used by the running task.
Note
|
| 2.7.2+Add content roots to PYTHONPATH | Select this check box to add all content roots of your project to the environment variable PYTHONPATH; |
| Add source roots to PYTHONPATH | Select this check box to add all source roots of your project to the environment variable PYTHONPATH; |
Toolbar
| Item | Shortcut | Description |
|---|---|---|
|
| InsertInsert | Click this button to add new configuration to the list. |
| DeleteDelete | Click this button to remove the selected configuration from the list. |
| Ctrl+DCtrl+D | Click this button to create a copy of the selected configuration. |
| Edit defaults | Click this button to edit the default configuration templates. The defaults are used for the newly created configurations. |
 or 
| Alt+UpAlt+Up or Alt+DownAlt+Down | Use these buttons to move the selected configuration or group of configurations (folder) up and down in the list.
The order of configurations or folders in the list defines the order, in which configurations appear in the Run/Debug drop-down list on the main toolbar. |
 | Use this button to create a new folder.
If one or more run/debug configurations have the focus, then the selected run/debug configurations 0 are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created. |
Common options
| Item | Description | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Name | In this text box, specify the name of the current run/debug configuration. This field does not appear for the default run/debug configurations. | ||||||||||||||||||
| Defaults | This node in the left-hand pane of the dialog box contains the default run/debug configuration settings. Select the desired configuration to change its default settings in the right-hand pane. The defaults are applied to all newly created run/debug configurations. | ||||||||||||||||||
| Temporary configurations limit | Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list. | ||||||||||||||||||
| Share |
Select this check box to make the run/debug configuration available to other team members.
The shared run/debug configurations are kept in separate xml files under .idea\runConfigurations folder, while the local run/debug configurations are kept in the .idea\workspace.xml. This check box is not available when editing the run/debug configuration defaults. | ||||||||||||||||||
| Single instance only | If this check box is selected, this run/debug configuration cannot be launched more than once.
Every time a new run/debug configuration is launched, PyCharm checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog box. If you click OK in the confirmation dialog box, the first instance of the runner will be stopped, and the next one will take its place. This make sense, when usage of certain resources can cause conflicts, or when launching two run/debug configurations of the same type consumes too much of the CPU and memory resources. If this check box is not selected, it is possible to launch as many instances of the runner as required. So doing, each runner will start in its own tab of the Run tool window. | ||||||||||||||||||
| Before launch | In this area, specify the actions to be performed prior to executing the current run/debug configuration.
|
