Run/Debug Configuration: JSTestDriver
The dialog box is available when the JSTestDriver plugin is activated. The plugin is bundled with WebStorm and activated by default. If not, enable it on the Plugins page of the Settings dialog box as described in Enabling and Disabling Plugins.
On this page:
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 WebStorm 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.
In this drop-down list, specify how WebStorm will get test runner configuration files.
|Directory||In this text box, specify the folder to look for test runner configuration files in. Type the path manually or click the Browse button and select the required folder in the dialog box, that opens.||All configuration files in directory|
|Matched configuration files||
This read-only field shows a list of all the ||All configuration files in directory|
|Configuration file||In this text box, specify the test runner configuration file to use. Type the path manually or click the Browse button and select the required file in the dialog box 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 text box, 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 WebStorm 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 WebStorm 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 drop-down 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.
|Alt+Insert||Click this button to add a new configuration to the list.|
|Alt+Delete||Click this button to remove the selected configuration from the list.|
|Ctrl+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 newly created configurations.|
|or||Alt+Up or Alt+Down||Use these buttons to move the selected configuration or 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.
|Sort configurations||Click this button to sort configurations in alphabetical order.|
|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.|
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
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, WebStorm 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||Specify which tasks must be performed before applying the run/debug configuration.
The specified tasks are performed in the order they appear in the list.