Run/Debug Configuration: JUnit Tests
JUnit run/debug configurations define how unit tests that are based on the JUnit testing framework should be run.
This run/debug configuration allows JUnit tests stored in MPS models to be run with JUnit.
Item | Description |
|---|---|
Test scope | Click one of the radio-buttons to pick the granularity of the test to run - the whole project, a particular module, model, class or a method. |
Project/Module/Model/ | Specify the MPS project/module/model/classes/methods that holds the tests to run |
Execute in the same process | Select this checkbox to indicate whether the tests should be run in the same MPS instance. |
Reuse caches | Indicates whether the generated artifacts, cached during the previous runs should be reused or deleted. Reusing the old caches of headless MPS instance when running tests cuts away a lot of time that would be needed to setup a test instance of MPS. It is possible to set and unset this option in the run configuration dialog. |
Save caches in | Specify the directory to save the caches in. By default, MPS chooses the temp directory. Thus with the checkbox Reuse caches selected, MPS saves its caches in the specified folder and reuses them whenever possible. If this checkbox is unselected, the directory is cleared on every run. |
VM parameters | Provide command-line arguments to the JVM |
Program parameters | Provide command-line arguments to the class |
Working directory | Override the default working directory with an explicit one |
Use alternative JRE | Explicitly specify a JRE distribution to use for running the class |
Common
When you edit a run configuration (but not a run configuration template), you can specify the following options:
Item | Description |
|---|---|
| Name | In this field, 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 Shift+Alt+F10. |
| Share through VCS | Select this checkbox to put the run/debug configuration under version control and make it available to other team members. The shared run/debug configurations are kept in separate xml files under .mps\runConfigurations folder, while the local run/debug configurations are kept in the .mps\workspace.xml. |
| Allow running in parallel | If this checkbox is selected, it is possible to launch a run configuration multiple times in parallel instead of rerunning it. Each runner will start in its own tab of the Run Tool Window or Debug Tool Window. When disabled, every time a new instance of the run/debug configuration is launched, MPS checks the presence of the other instances of the same run/debug configuration, and displays a confirmation dialog. If you click OK in the confirmation dialog, the first instance of the runner will be stopped, and the next one will take its place. This makes sense when launching two instances of run/debug configurations of the same type consumes too much of the CPU and memory resources.. |
Toolbar
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.
Item | Shortcut | Description |
|---|---|---|
 | 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. | |
| Alt+Up/Alt+Down | 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 Then, to move a configuration into a folder, between the folders or out of a folder, use drag or To remove grouping, select a folder and click | |
 | Click this button to sort configurations in the alphabetical order. |
/
, and specify the folder name. If only a category is in focus, an empty folder is created. Before Launch
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.
Item | Shortcut | Description |
|---|---|---|
| Alt+Insert | 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 | 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 isn't shown. However, when the configuration is running, you can open the corresponding tool window for it yourself by pressing Alt+4 or Alt+5. |