1. Docs
  2. Administration
  3. Project settings
  4. Mobile Config

Mobile Config

Mobile Config tells SmartestQA where a mobile project’s app runs and how to start it: on a phone or emulator next to your agent, on SmartTest Device Farm, or on AWS Device Farm or BrowserStack real devices.

7 min read Updated CustomersAdmins

In short

On this page you can

  • Choose the execution mode: Local device, SmartTest Device Farm, AWS Device Farm or BrowserStack.
  • Fill the Android package and activity, or the iOS bundle ID, by reading them from an APK or IPA.
  • Connect AWS Device Farm or BrowserStack with your keys and pick the devices to run on in parallel.
  • Reach apps behind a VPN with BrowserStack Local or an AWS VPC, and test the connection.
  • Pick the app SmartTest Device Farm installs before each run.

How to use it

  1. Open Configuration › Project Panel › Mobile Config.
  2. Click the card of the mode you use; the fields of that mode appear.
  3. Fill the fields; use Read APK or Read IPA to fill app IDs from the file.
  4. For AWS or BrowserStack, save your keys first, then reopen the card to load the device list and pick devices.
  5. Click Save Configuration and wait for “Mobile configuration saved successfully”.

The section appears for MOBILE, ANDROID and IOS projects. A MOBILE project has an Android/iOS switch and keeps a configuration for each platform. First steps for a phone on your desk are in Connect your app; how to capture screens is in Discover › Mobile & desktop.

Execution modes#

CardShownThe app runs onYou need
SmartTest Device Farm · “Our devices”Only when your company’s licence includes the Device Farm rightSmartestQA’s own real phonesAn app in the Device Farm App Library
Local device · “Your agent”AlwaysA phone or emulator connected to the computer with your agentThe agent and Appium Server running there
AWS Device Farm · “Real devices”AlwaysDevices in your AWS accountAWS keys, a Device Farm project, the app uploaded
BrowserStack · “Real devices”AlwaysDevices in your BrowserStack accountBrowserStack user name and access key, the app uploaded there

The mode that is saved is the last one of Local device, AWS Device Farm and BrowserStack you clicked before Save Configuration. The SmartTest Device Farm card only shows its own settings; pipelines choose Device Farm runs themselves. When the page opens it shows the Local device view first; click your mode’s card to see its fields.

Local device#

FieldWhat to enterDefault
Appium Server URLThe Appium server next to your device: “URL of your Appium server (default: http://localhost:4723)”.http://localhost:4723

Android Configuration#

“The device is chosen at run time (Run / Schedule / Appium Inspector) — no device setting is stored here.”

FieldWhat to enterRequired
App PackageThe Android package name, for example com.example.app.No
App ActivityThe activity started on launch, for example .MainActivity.No

Read APK next to App Package reads an .apk file and overwrites App Package and App Activity with what it finds. Files up to 200 MB.

iOS Configuration#

FieldWhat to enterDefault
Connected DevicePick a simulator or USB device found by your agent (grouped as USB Connected and Simulator). Refresh with “Refresh device list”. It fills the three fields below.—
Device Name, Platform Version, Device UDIDRead only, filled from the picked device.iPhone 15, 17.0, empty
Bundle ID (Optional)The iOS bundle identifier. Read IPA fills it from an .ipa file and overwrites it.Empty
Xcode Org ID (Optional)Your Apple Developer Team ID, for real devices.Empty
Xcode Signing IDThe code signing identity.iPhone Developer

The device picker appears only while your agent answers. If it says no devices were found, check that the agent is running and the device is connected; see No devices found.

SmartTest Device Farm#

When your company’s licence includes the Device Farm right, the card “SmartTest Device Farm — App to install (project default)” picks the app installed on farm devices before a run: “Android app (installed before run)” or “iOS app (installed before run)”. Choose No app install to skip. An app with the same version already on the device is not installed again.

  • The list comes from the Device Farm App Library of your company, filtered by platform.
  • App details (package / activity) shows the package, activity or bundle ID read from the app record. These values are what the run uses; change them in the App Library, not here.
  • A pipeline can pick a different app for its own runs.

AWS Device Farm#

BlockFieldWhat to enter
AWS CredentialsAWS Access KeyYour access key ID (AKIA…).
AWS Secret KeyThe secret access key.
AWS RegionUS West (Oregon) (default), US East (N. Virginia), EU (Ireland), Asia Pacific (Tokyo).
Project ConfigurationAWS Project NameThe name of your AWS Device Farm project.
Device Pool Name (Optional)A device pool; empty = the default pool.
Test DevicesRequired. The devices to run on. Each selected device runs the tests in parallel.
AWS Device Farm App ARNFilled by the upload button, or pasted from the AWS console. An existing ARN is reused, so the app is not uploaded again.
VPC Settings (Optional)VPC IDOnly if the app under test needs your private network. The VPC must be connected to your network by Site-to-Site VPN or Direct Connect.
Subnet IDs (CSV)One or more subnet IDs, comma-separated.
Security Group IDs (CSV)One or more security group IDs, comma-separated.
  1. Save the keys and project name

    Enter the AWS fields and click Save Configuration. Saving needs at least one test device, so pick one from the built-in list first.

  2. Reopen the card

    Click the AWS Device Farm card again. The device list now comes from your AWS account (“{n} devices loaded from your AWS account”). Busy devices are marked.

  3. Upload the app

    Click “Upload APK to AWS Device Farm” (or IPA). The button works once the keys are saved and a project name is set.

    “App uploaded — the ARN was filled in automatically.” Empty App Package, App Activity or Bundle ID fields are filled from the file; values you typed are kept.

  4. Pick devices and save

    Select the devices and save again.

Some brands may not run

Xiaomi, Huawei and Honor devices are marked with a warning, for example “MIUI/HyperOS may block Appium Settings install. Test may fail.” Prefer other models. More than 5 devices use up AWS minutes fast.

BrowserStack#

BlockFieldWhat to enter
BrowserStack CredentialsUsernameFrom BrowserStack Dashboard › ACCESS KEY.
Access KeyFrom the same page.
Device & OSDevice & OSOne or more devices; search by name. The list loads after the keys are saved.
Application UploadApp URL (bs://...)Upload the app in BrowserStack (App Automate › Upload) and paste the bs://… URL it returns.
Dashboard Metadata (Optional)Project NameGroups runs on the BrowserStack dashboard. Default SmartTest.
Build NameFor example a sprint or release name.
Debug LogsNetwork Logs, Device Logs, Appium LogsLogs BrowserStack keeps for each session. All on by default.
BrowserStack LocalUse BrowserStack LocalFor apps behind a VPN or firewall. Start the BrowserStackLocal program in your network first.
Force local (route all traffic through tunnel)Sends all traffic through the tunnel.
BrowserStack Local IdentifierMust match the --local-identifier you started BrowserStackLocal with.
How many devices you can pickBrowserStack and AWS device selection
BrowserStack: max devices = parallel sessions of your BrowserStack plan   (1 until the plan is loaded)
              parallel sessions opened = devices selected
AWS:          parallel jobs = devices selected                             (at least 1)

Example: the plan chip shows Team • 5x parallel. You can select up to 5 devices; selecting 3 shows “3/5 devices selected — 3 parallel sessions will open”. If the plan has not loaded yet, only 1 device can be selected; save the keys and reopen the card.

VPN status and Test Connection#

On the AWS and BrowserStack cards a chip shows VPN active or Public. It turns active when Use BrowserStack Local is on or a VPC ID is filled. Test Connection opens VPN Connectivity Test (“may take 15-30 sec”) and lists each check as OK, WARN or FAIL with a suggestion. It uses the values on screen; when both are set, BrowserStack Local is tested.

Save Configuration#

Save Configuration in the header saves every card at once. It is disabled, with the reason in its tooltip, when:

  • the mode is AWS Device Farm and no device is selected: “Select at least 1 test device for AWS Device Farm”;
  • the mode is BrowserStack and no device is selected: “Select at least 1 test device for BrowserStack”;
  • more BrowserStack devices are selected than the plan allows: “Plan limit exceeded: {count} devices selected, {max} allowed. Reduce selection or upgrade plan.”

Success: “Mobile configuration saved successfully”. Failure: “Failed to save mobile configuration”.

Keys are never shown again

After saving, the AWS keys and the BrowserStack access key show as dots. Leave them to keep the saved value; clear the field and type a new key to replace it. An empty field keeps the saved key, so a key cannot be removed from this screen.

If something goes wrong#

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai