Appium技术疑问：启动不打开应用/Activity及锁屏解锁场景测试

Great question—Appium absolutely can handle full-device security policy testing, you just need to tweak your approach a bit to get past those lockscreen and launcher hurdles. Let’s break down solutions to your specific issues:

The problem with specifying the launcher app as your entry point is that Appium tries to launch it immediately, but can’t interact with the lockscreen first. Instead, disable auto-launch and handle the lockscreen + launcher manually:

• Set autoLaunch to false in your desired capabilities. This tells Appium not to auto-launch any app on startup.
• Initialize the driver, then first unlock the device using low-level UI interactions (instead of the one-time unlockType/unlockKey). For example, if using a PIN lock:

  // Wake up the device
  driver.executeScript("mobile: shell", ImmutableMap.of("command", "input keyevent 26"));
  driver.executeScript("mobile: shell", ImmutableMap.of("command", "input swipe 500 1500 500 500")); // Swipe to unlock prompt
  
  // Locate the PIN input fields (adjust IDs to match your device's UI)
  List<WebElement> pinFields = driver.findElements(By.id("com.android.systemui:id/pin_entry_text"));
  for (WebElement field : pinFields) {
      field.sendKeys("1234"); // Replace with your test PIN
  }
  driver.findElement(By.id("com.android.systemui:id/ok_button")).click();
  

• Once unlocked, launch the launcher app manually via adb or Appium's startActivity method:

  driver.startActivity(new Activity("com.android.launcher3", "com.android.launcher3.Launcher"));
  

  (Note: The launcher package/activity varies by device—use adb shell dumpsys window | grep mCurrentFocus to find the correct values.)

The built-in unlock capabilities are too limited for complex scenarios like repeated failed attempts. Instead, build manual workflows that simulate each step:

• Reset the lockscreen state before each test: Use adb commands to set a known lock type/pin, so your tests start from a consistent state:

  # Set a PIN lock (replace 1234 with your test PIN)
  adb shell locksettings set-pin 1234
  # Lock the device
  adb shell input keyevent 26
  

• Simulate repeated failed PIN attempts: Loop through entering an incorrect PIN, confirming, and handling any error prompts. For example:

  for (int i = 0; i < 10; i++) {
      // Wake and navigate to PIN screen (same as step 1)
      driver.executeScript("mobile: shell", ImmutableMap.of("command", "input keyevent 26"));
      driver.executeScript("mobile: shell", ImmutableMap.of("command", "input swipe 500 1500 500 500"));
  
      // Enter wrong PIN
      List<WebElement> pinFields = driver.findElements(By.id("com.android.systemui:id/pin_entry_text"));
      for (WebElement field : pinFields) {
          field.sendKeys("0000"); // Wrong PIN
      }
      driver.findElement(By.id("com.android.systemui:id/ok_button")).click();
  
      // Wait for error prompt and dismiss it (adjust selector as needed)
      WebElement errorPrompt = driver.findElement(By.id("com.android.systemui:id/error_msg"));
      new WebDriverWait(driver, 10).until(ExpectedConditions.visibilityOf(errorPrompt));
      driver.findElement(By.id("com.android.systemui:id/dismiss_button")).click();
  }
  // After 10 attempts, verify the device wipe prompt/action occurs
  WebElement wipePrompt = driver.findElement(By.id("com.android.settings:id/wipe_device_button"));
  new WebDriverWait(driver, 30).until(ExpectedConditions.visibilityOf(wipePrompt));
  

• Use emulator snapshots for repeatability: If testing on an emulator, take a snapshot before starting the failed attempts test. After each test run, restore the snapshot to reset the device to its pre-wipe state without reconfiguring everything from scratch.

• Use UiAutomator2 as your driver: It has better support for system-level UI elements (like lockscreen controls) compared to other drivers.
• Increase timeout values: Set newCommandTimeout to a higher value (e.g., 60) in your desired capabilities to avoid Appium timing out during long workflows like 10 failed unlock attempts.
• Locate elements with care: System UI element IDs can vary by Android version and manufacturer. Use tools like uiautomatorviewer (part of Android SDK) to inspect lockscreen elements and get the correct selectors.

To answer your final question: Appium is absolutely suitable for full-device security testing—you just need to move beyond the basic app-focused capabilities and leverage low-level UI interactions, adb integrations, and careful state management.

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