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.
Click here for the description of the options that are common for all run/debug configurations.
|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/Classes/Methods||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. |
Onselect this checkbox to start a new invisible (headless) MPS process in the background to run the tests.
Running test in the same process is usually much faster.
|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 |
|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|
|N/A||Click this button to add a new configuration to the list.|
|N/A||Click this button to remove the selected configuration from the list.|
|N/A||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||N/A or N/A||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.|
|Share|| 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, MPS 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 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. |