Android真机Appium测试中动态编程修改Desired Capabilities咨询

Hey there! I’ve dealt with similar headaches managing fleets of Android devices for functional testing, so I totally get where you’re coming from. Here are a few practical, code-based approaches to dynamically modify device capabilities programmatically:

ADB is your go-to tool for scriptable, direct device tweaks. Most common capabilities can be adjusted via shell commands, which you can wrap in scripts (Python, Bash, etc.) to automate across your device fleet.

• Modify system properties: Many device identifiers and settings are stored as system properties. For example, to change the device model name:

  adb shell setprop ro.product.model "TestDevice_X"
  

  Verify the change with:

  adb shell getprop ro.product.model
  

  Note: Some properties require root access, but many high-level ones (like model, manufacturer, or software version) can be modified on test devices with developer options enabled, no root needed.

• Adjust display capabilities: To dynamically change screen resolution:

  adb shell wm size 1440x2960
  

  Reset to the device's default resolution:

  adb shell wm size reset
  

If you’re using Appium for test automation, you can dynamically override capabilities per test run by updating the desired capabilities object before initializing the driver. This is perfect for switching between devices with different test configurations.

Here’s a quick Python example:

from appium import webdriver

def init_device_driver(device_id, custom_caps):
    # Base capabilities for all tests
    base_caps = {
        "platformName": "Android",
        "deviceName": device_id,
        "automationName": "UiAutomator2",
        "noReset": True
    }
    # Merge custom capabilities into the base set
    base_caps.update(custom_caps)
    return webdriver.Remote("http://localhost:4723/wd/hub", base_caps)

# Example: Switch between two devices with different app targets and model spoofs
driver_deviceA = init_device_driver("0123456789ABCDEF", {
    "appPackage": "com.myapp.staging",
    "appActivity": "com.myapp.MainActivity",
    "ro.product.model": "GalaxyS23"
})

driver_deviceB = init_device_driver("9876543210FEDCBA", {
    "appPackage": "com.myapp.production",
    "appActivity": "com.myapp.LaunchActivity",
    "ro.product.model": "Pixel7"
})

Pro tip: Fetch connected device IDs automatically with adb devices and loop through them to apply different capability sets in bulk.

Build a lightweight wrapper to abstract device selection and capability changes. This is ideal for managing large fleets, as you can batch-apply configurations without manual intervention.

Here’s a simplified Python snippet to get you started:

import subprocess
import json

def apply_device_configs(device_id, config):
    for cap, value in config.items():
        if cap.startswith("ro."):
            # Modify system property
            subprocess.run(["adb", "-s", device_id, "shell", "setprop", cap, value])
        elif cap == "screen_density":
            # Adjust display density
            subprocess.run(["adb", "-s", device_id, "shell", "wm", "density", value])

# Load configuration from a JSON file (map device IDs to custom capabilities)
with open("device_fleet_configs.json") as f:
    fleet_configs = json.load(f)

# Apply configs to all connected devices
connected_devices = subprocess.check_output(["adb", "devices"]).decode().splitlines()[1:]
for device_line in connected_devices:
    device_id = device_line.split("\t")[0]
    if device_id and device_id in fleet_configs:
        apply_device_configs(device_id, fleet_configs[device_id])

Quick Notes to Keep in Mind #

• Always test changes on a single device first to avoid breaking your entire test fleet.
• Hardware-specific capabilities (like camera resolution) can’t be modified without root access, so focus on the software/configuration props that matter most to your tests.
• When using Appium, restart the driver instance each time you switch devices to ensure new capabilities take effect.

内容的提问来源于stack exchange，提问作者user9730175