Run/Debug Configuration: JSTestDriver
The dialog box is available when the JSTestDriver plugin is activated. The plugin is not bundled with AppCode, but it can be installed from the JetBrains plugin repository as described in Managing Plugins.
Before you start
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 AppCode 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 AppCode will get test runner configuration files. |
In this text box, 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 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
In this text box, specify the test runner configuration file to use. Type the path manually or click Browse and select the required file in the dialog box that opens.
JS test file
In this area, appoint the test server to run tests against.
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 AppCode 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 AppCode 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. |
When you edit a run configuration (but not a run configuration template), you can specify the following options for it:
In this text box, specify the name for the run/debug configuration. The name will help you identify the created configuration when you choose to edit it later, or when you invoke it, for example, from the Run popup (⌃⌥R).
Select this checkbox 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.
Allow running in parallel
When disabled, every time a new run/debug configuration is launched, AppCode 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 makes sense when the 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 checkbox is selected, it is possible to launch as many instances of the run/debug configuration as required. So doing, each runner will start in its own tab of the Run Tool Window or Debug Tool Window.
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.
Create a run/debug configuration.
Delete the selected run/debug configuration. Note that you cannot delete default configurations.
Create a copy of the selected run/debug configuration. Note that you create copies of default configurations.
View and edit the default template for the selected run/debug configuration. The templates are 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-and-drop or and buttons.
To remove grouping, select a folder and click .
Click this button to sort configurations in the alphabetical order.
Under the Templates node in the tree view of run configurations, you can select a run configuration template and edit its default settings. This will not affect the configurations that are already created, but will be used as defaults when creating new configurations of the corresponding type.
When you select the Templates node itself, you will be able to adjust general settings that apply to all run/debug configurations:
Configurations available in Run Dashboard
In this section you can create a list of run configurations available in the Run Dashboard — a tool window that helps you execute and manage multiple run/debug configurations.
Note that the dashboard will only display the configuration types for which you have created one ore more configurations.
Thus, if you add a configuration type for which no configurations exist in the project, this type will not be displayed on the dashboard until you create a configuration of this type.
Confirm rerun with process termination
|The behavior of this checkbox depends on whether the Single instance only option is selected for a particular run/debug configuration. |
Temporary configurations limit
Specify the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.
Before Launch options
In this area you can specify tasks that must be 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:
Click this icon to remove the selected task from the list.
Click this icon to edit the selected task. Make the necessary changes in the dialog that opens.
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, the tool window isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing ⌘4 or ⌘5.