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/ 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 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 settings

When you edit a run configuration (but not a run configuration template), you can specify the following options:

Item	Description
Name	Specify a name for the run configuration to quickly identify it among others when editing or running.
Allow multiple instances	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, MPS suggests stopping the running instance and starting another one. This is helpful when a run 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 MPS stores run configuration settings in .idea/workspace.xml.

Item

Description

Name

Specify a name for the run configuration to quickly identify it among others when editing or running.

Allow multiple instances

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, MPS suggests stopping the running instance and starting another one. This is helpful when a run 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 MPS stores run configuration settings in .idea/workspace.xml.

Before launch

In this area, you can specify tasks to 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: Run Another Configuration: select to execute another run/debug configuration and wait until it finishes before starting the current configuration. If you want to run several configurations in parallel, use a compound run/debug configuration.
	`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 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`.
Focus tool window		Select this checkbox to automatically move focus to the Run or the Debug tool window when you start the run/debug configuration.

Logs

The following options are related to logging the execution of this configuration. For more information, refer to .

Item	Description
Specify logs to be shown in the console	Specify which log files to display while running the application. Click to add a new log. In the Edit Log Files Aliases dialog, configure the following: Alias: The name of the tab where the log will be displayed. Log File Location: Specify the path to the log file or an Ant pattern. If several files of a rolling log match the pattern, MPS will display the most recent one. Show all files coverable by pattern: Show all logs that match the pattern. For logs in the table, you can configure the following options: Is Active: Display the specified log file. Skip Content: Do not display old log messages from previous runs.
Save console output to file	Save the console output to the specified location. Type the path manually or click the browse button and point to the desired location in the dialog that opens.
Show console when a message is printed to stdout	Activate the console when the application writes to the standard output stream.
Show console when a message is printed to stderr	Activate the console when the application writes to the standard error stream.

03 April 2025