Run/Debug Configuration: JSTestDriver

In this list, specify how JetBrains DataSpell will get test runner configuration files.

• All configuration files in directory: select this option to use all the test runner configuration files in a specific folder.

• Configuration file: select this option to use a specific test runner configuration file.

• JavaScript test file: select this option to have tests from a specific file executed using one of the previously defined configuration files.

• Case: select this option to run a specific test case using one of the previously defined configuration files.

• Method: select this option to run a specific test method using one of the previously defined 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.

Click this button to check that the specified test server is accessible.

The server must be running. Start the server from JetBrains DataSpell or manually, according to the server-specific instructions.

From this list, choose the browser to debug the specified tests in when two browsers are captured at a time. The available options are:

• Chrome

• Firefox

In this area, create a list of files to be skipped during coverage analysis.

• To add an item to the list, click the Add button and choose the required file in the dialog that opens.

• To delete a file from the list so coverage is measured for it, select the file and click the Remove button .

Name

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

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 icon to add one of the following available tasks:

• Run External tool: select to run an external application. In the dialog that opens, select one or multiple applications you want to run. If it is not defined in JetBrains DataSpell yet, add its definition.

• Run Another Configuration: select to execute another run/debug configuration. In the dialog that opens, select the configuration to be run.

• Run File Watchers: select this option to have JetBrains DataSpell apply all the currently active File Watchers.

• Run Grunt task: select this option to run a Grunt task.

  In the Grunt task dialog that opens, specify the Gruntfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Grunt tool.

  Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the grunt-cli package.

• Run Gulp task: select this option to run a Gulp task.

  In the Gulp task dialog that opens, specify the Gulpfile.js where the required task is defined, select the task to execute, and specify the arguments to pass to the Gulp tool.

  Specify the location of the Node.js interpreter, the parameters to pass to it, and the path to the gulp package.

• Run npm Script: select this option to execute an npm script.

  In the NPM Script dialog that opens, specify the npm run/debug configuration settings.

• Compile TypeScript: select to run the built-in TypeScript compiler and thus make sure that all the changes you made to your TypeScript code are reflected in the generated JavaScript files. In the TypeScript Compile Settings dialog that opens, select or clear the Check errors checkbox to configure the behaviour of the compiler in case any errors are detected:

  • If the Check errors checkbox is selected, the compiler will show all the errors and the run configuration will not start.

  • If the Check errors checkbox is cleared, the compiler will show all the detected errors but the run configuration still will be launched.

By default this checkbox is selected and the Run or the Debug tool window opens when you start the run/debug configuration.

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.