Run/Debug Configuration: JSTestDriver
In this tab, specify the tests to run, the configuration files to use, and the server to run the tests against.
In this area, tell CLion where to find the tests to execute and how to get test runner configuration files that define which test files to load and in which order. The main approaches are:
Specify the location of one or several previously created configuration files.
Point at the target test file, test case, or test method, and then specify the location of the corresponding configuration file.
The way to find tests and configuration files is defined in the Test list. This choice determines the set of other controls in the area.
In this list, specify how CLion will get test runner configuration files.
In this field, specify the folder to look for test runner configuration files in. Type the path manually or click Browse and select the required folder in the dialog, that opens.
|All configuration files in directory|
|Matched configuration files||This read-only field shows a list of all the .jstd and jsTestDriver.conf test runner configuration files detected in the specified folder.||All configuration files in directory|
|Configuration file||In this field, specify the test runner configuration file to use. Type the path manually or click Browse and select the required file in the dialog that opens.||Configuration file|
In this area, appoint the test server to run tests against.
|At address||Choose this option to have the test execution handles by a remote test server. In the field, specify the URL address to access the server through.|
|Running in IDE||Choose this option to have test execution handles through the JSTestDriver server that comes bundled with CLion and can be launched from it.|
Click this button to check that the specified test server is accessible.
The server must be running. Start the server from CLion or manually, according to the server-specific instructions.
In this tab, appoint the browser to debug the unit test in when two or more browsers are captured simultaneously.
From this list, choose the browser to debug the specified tests in when two browsers are captured at a time. The available options are:
In this tab, specify the files that you do not want to be involved in coverage analysis.
|Exclude file path|
In this area, create a list of files to be skipped during coverage analysis.
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Specify a name for the run/debug configuration to quickly identify it when editing or running the configuration, for example, from the Run popup Alt+Shift+F10.
Allow parallel run
Select to 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, CLion suggests to stop the running instance and start another one. This is helpful when a run/debug 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 CLion stores run configuration settings in .idea/workspace.xml.
The tree view of run/debug configurations has a toolbar that helps you manage configurations available in your project as well as adjust default configurations templates.
|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.|
|View and edit the template (that is, the default run/debug configuration settings). The templates are displayed under the Templates node and used for newly created configurations.|
Move the selected run/debug configuration up and down in the list.
The order of configurations in the list defines the order, in which the configurations appear when you choose a run/debug configuration.
Default templates of run/debug configurations are always sorted alphabetically.
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.|
In this area you can specify tasks that must be performed before starting the selected run/debug configuration. The tasks are performed in the order they appear in the list.
Click this icon to add one of the following available tasks:
|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|
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.