Run/Debug Configuration: Android Test

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

The dialog box consists of three tabs:

General
Emulator
Logcat

General Tab

Item	Description
Module	From this drop-down list, select the module to which this configuration will be applied.
Test	In this area, specify the location of tests that you want to apply: All in module: select this option if you want to launch all tests from the selected module. All in package: select this option is you want to launch all tests from a specific package. In the Package text box, specify the package where tests are located. Type the package name manually or click Browse and select the desired package in the dialog that opens. Class: select this option if you want to launch tests of a specific class. In the Class text box, specify the required class. Type the class name manually or click Browse and select the desired class in the dialog that opens. Method: select this option if you want to launch a specific test method. In the Class text box, specify the class to which this method belongs. In the Method text box, specify the desired method. Type the names manually or click Browse and select the desired class and method in the dialog that opens.
Specific instrumentation runner	In this text box, specify the location of the desired instrumentation runner. Type the path manually or click Browse and select the location in the dialog that opens.
Deployment Target Options	In this area, select the type of device to run/debug the application on. The available options are: Show Device Chooser Dialog: select this option to have IntelliJ IDEA display the Choose Device dialog box upon the application start. If you want to automatically use the device chosen through the Choose Device dialog in the future, select the Use same device for future launches option. USB Device: select this option to have IntelliJ IDEA detect a plugged-in USB device upon the application start. Selecting the Show Device 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. Emulator: select this option to use one of the configured device emulators. From the Prefer Android Virtual Device drop-down list, select a virtual device that will be used to run/debug the specified activity. If you want to add/edit a virtual device configuration, click the Browse button to launch the Android Virtual Device (AVD) Manager (see Managing Virtual Devices for details).

Emulator Tab

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

Item	Description
Network Speed	From this drop-down list, select the network transfer rate to be emulated.
Network Latency	Use this drop-down list to specify the time delay between the initial input and the output. You can select between the following latency levels: None: no latency GPRS: GPRS (min 150, max 550 milliseconds) EDGE: EDGE/EGPRS (min 80, max 400 milliseconds) UMTS: UMTS/3G (min 35, max 200 milliseconds)
Wipe user data	Select this checkbox 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 checkbox if you do not want an animated boot screen displayed upon the emulator start-up.
Additional command line options	In this field, type the additional options to be passed to the emulator via the command line. For lengthy command lines, click the button and type the text in the Emulator Additional Command Line Options dialog that opens.

Logcat Tab

Item	Description
Clear log before launch	Select this checkbox if you want data from previous sessions to be removed from the log before starting the application.

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. 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, or 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 otherwise.

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.

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, or 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 otherwise.

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 settings) for the selected run/debug configuration. 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 , 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 button to sort configurations in the alphabetical order.

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: 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 IntelliJ IDEA yet, add its definition. For more information, see External tools and External Tools. Run Another Configuration: select to execute another run/debug configuration. In the dialog that opens, select the configuration to be run. Build: select to compile the specified module. The Build Module command will be executed. If an error occurs during compilation, IntelliJ IDEA won't attempt to start the run/debug configuration. Build Project: select to compile the entire project. The Build Project command will be executed. If an error occurs during compilation, IntelliJ IDEA won't attempt to start the run/debug configuration. Build, no error check: the same as the Build option, but IntelliJ IDEA will try to start the run/debug configuration irrespective of the compilation results. Build Artifacts: select this option to build an artifact or artifacts. In the dialog that opens, select the artifact or artifacts that should be built. Launch Web Browser: select this option to have a browser started. In the dialog that opens, select the type of the browser and provide the start URL. Also, specify if you want the browser be launched with JavaScript debugger. Run Ant target: select this option to run an Ant target. In the dialog that opens, select the target to be run. 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 Maven Goal: select this option to run a Maven goal. In the dialog that opens, select the goal to be run. 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. Start React Native Bundler: select this option to run the bundler automatically, as part of a running or debugging session. by default, this is done through `react-native start`. If your application uses Expo, you need to run the development server via the `start` npm task. To do that, click , then in the Configure React Native dialog, choose npm script and select start from the list. 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. Generate CoffeeScript Source Maps: select this option to generate the source maps for your CoffeeScript sources. In the dialog that opens, specify where your CoffeeScript source files are located. Upload files to Remote Host: select this option to have the application files automatically uploaded to the server according to the default server access configuration. Run Remote External tool: adds a remote SSH external tool. Run Rake task: add a Rake task to be executed prior to running or debugging. To choose a Rake task, click the browse button , and select the desired task from the list of available tasks. Note that code completion is available here. Run JRuby compiler: choose this option to execute JRuby compiler with the specified target path, compiler process heap size, and command line parameters (if any).
	`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`.

Last modified: 17 October 2019