IntelliJ IDEA 12.1.0 Web Help

Some features described here are available in Ultimate edition only.

Use this dialog box to configure testing of Android applications and activities on actual and virtual devices.

Click here for the description of the options that are common for all run/debug configurations.

The dialog box consists of three tabs:

General tab

ItemDescription
ModuleFrom this drop-down list, select the module to apply the configuration to.
TestIn this area, specify where in your project IntelliJ IDEA should search for tests to apply:
  • All in module - select this option to have all the tests available in the current module launched.
  • All in package - select this option to have test classes of a specific package launched. In the Package text box, specify the package to look for tests in. Type the package name manually or click the Browse button browseButton.png and select the desired package in the tree view, that opens.
  • Class - select this option to have tests of a specific class launched. In the Class text box, specify the desired class. Type the class name manually or click the Browse button browseButton.png and select the desired class in the tree view, that opens.
  • Method - select this option to have a specific test method launched.
    • In the Class text box, specify the class in which the desired test method is. Type the file name manually or click the Browse button browseButton.png and select the desired class in the tree view, that opens.
    • In the Method text box, specify the desired method.
Specific Instrumentation Runner In this text box, specify the location of the desired instrumentation runner. Type the path manually or click the Browse button browseButton.png and select the desired location in the tree view, that opens.
Deploy application
  • When this check box is selected, the current application is deployed on the selected target device and launched according to the launch settings.
  • When this check box is cleared, the previously deployed application is launched. If no application is deployed on the device, an error is reported.
Target Device In this area, choose the type of device to run/debug the application on. The available options are:
  • Show chooser dialog: choose this option have IntelliJ IDEA display the Choose Device dialog box when the application is already started.
  • USB device: choose this option to have IntelliJ IDEA detect a plugged in USB device upon the application start.
  • Emulator: choose this option to use one of the configured emulators and choose the relevant configuration in the Prefer Android Virtual Device drop-down list.

Note

Selecting the Show chooser dialog or USB device option may be helpful if you are going to run the application on a physical device which will be plugged in later and therefore the set of available devices cannot be foreseen.

Prefer Android Virtual DeviceFrom this drop-down box, select the virtual device configuration to run or debug the specified activity.

The drop-down list is available only if the Emulator check box is cleared.

Browse browseButton.pngClick this button to open the Select Android Virtual Device dialog box, where you can appoint a device to launch upon the future session start-up with the configuration being specified

Emulator tab

In this tab, specify additional configuration settings for launching the Android emulator.

ItemDescription
Network Speed From this drop-down list, select the network transfer rate to be simulated.
Network Latency Use this drop-down list to specify the time delay between the initial input and the output.
Wipe user data Select this check box to have the contents of the user-data image copied to the new user-data disk image while resetting the image. By default, the <system>/userdata.img is copied.
Disable boot animation Select this check box if you do not want an animated boot screen displayed upon the emulator start-up.
Additional command line options In this text box, type the additional options to be passed to the emulator via the command line. For lengthy command lines, click the editorIcon.gif button and type the text in the Additional Command Line Options dialog box, that opens.

Logcat tab

ItemDescription
Clear log before launch Select this check box to have the data from previous sessions removed from the log file before starting the application.

Toolbar

ItemShortcutDescription
add InsertInsert Click this button to add new configuration to the list.
delete DeleteDelete Click this button to remove the selected configuration from the list.
copy Ctrl+DCtrl+D Click this button to create a copy of the selected configuration.
settings Edit defaultsClick this button to edit the default configuration templates. The defaults are used for the newly created configurations.
arrowUp or arrowDown Alt+UpCommand Up or Alt+DownCommand Down Use these buttons to move the selected configuration or group of configurations (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.

folder Use this button to create a new folder.

If one or more run/debug configurations have the focus, then the selected run/debug configurations 0 are automatically moved to the newly created folder. If only a category has the focus, then an empty folder is created.

Common options

ItemDescription
NameIn 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.
Temporary configurations limit Specify here the maximum number of temporary configurations to be stored and shown in the Select Run/Debug Configuration drop-down list.
Share Select this check box to make the run/debug configuration available to other team members.

If the directory-based project format is used, the settings for a run/debug configuration are stored in a separate xml file in the .idea\runConfigurations folder if the run/debug configuration is shared and in the .idea\workspace.xml file otherwise.

If the file-based format is used, the settings are stored in the .ipr file for shared configurations or in the .iws file for the ones that are not shared.

This check box is not available when editing the run/debug configuration defaults.

Single instance onlyIf this check box is selected, this run/debug configuration cannot be launched more than once.

Every time a new run/debug configuration is launched, IntelliJ IDEA 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 make sense, when 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 launchIn this area, specify the actions to be performed prior to executing the current run/debug configuration.
ItemKeyboard shortcutDescription
addAlt+InsertCommand N; Command Enter Click this button to add one of the tasks to be executed prior to launching the application. The possible tasks are:
  • Run External tool: Add this task to have IntelliJ IDEA launch the specified third-party tool prior to running or debugging. To appoint a tool to launch, select it in the External Tools dialog box that opens.
  • Make: Add this task to compile the project automatically, prior to running or debugging. This option helps you ensure that all changes are included and compiled. If there are no changes, the program will just run.
  • Build Artifacts: Add this task to build the specified artifacts prior to running or debugging. To define the artifacts to be built, click the Browse button browse and select the desired artifact from the list of artifacts configured for the current module. To learn more about configuring artifacts, refer to Artifacts section.
  • Run Another Configuration: Add this task to choose one of the already defined temporary or permanent run/debug configurations.
  • Run Ant target:Add this task to build the specified Ant target prior to running or debugging. To define an Ant target, click Browse button browse and select the desired target from the list of existing targets. To learn more about Ant support, refer to Ant Support section.
  • Run Maven goal: Add this task to execute the specified Maven goal prior to running or debugging. To define a Maven goal to be executed, click Browse button browse and select the desired goal from the list. To learn more about Maven support, refer to Maven Support section.
deleteAlt+DeleteCommand Delete Click this button to remove selected task from the list.
edit1EnterEnter Click this button to open the selected task for editing.
arrowUp or arrowDownAlt+UpCommand Up or Alt+DownCommand Down Click these buttons to move the selected task one line up or down.

Note that Before launch actions are performed in the order they are specified in the run/debug configuration dialog.

Show this pageSelect this check box to always show the Edit Run/Debug Configuration dialog prior to launching the current run/debug configuration.
If this check box is not selected, run/debug configuration will be launched silently.

See Also

Concepts:

Procedures:

Reference:

Web Resources: