Mobile/Fennec/Android/Testing: Difference between revisions

Mobile/Fennec/Android/Testing (view source)

Revision as of 21:40, 27 July 2018

1,376 bytes removed , 27 July 2018

→‎Device Managers

Gbrown

Confirmed users

1,759

edits

@@ Line 362: / Line 362: @@
 To make Robocop (for example) run on ''emulator-5556'':
      $ mach robocop --deviceSerial=emulator-5556 # Runs your tests as normal
-== Device Managers ==
-Most test suites - mochitests, reftests, xpcshell tests, and others - use a "device manager" module to communicate with the remote device. There are two device manager implementations: ADB and SUT.
-The ADB device manager uses the adb command from the Android SDK to communicate with the remote device. To use the ADB device manager:
-* ensure the adb command is in your shell's PATH
-* mach test commands use adb by default; if running tests with make, set environment variable DM_TRANS=adb
-The SUT device manager uses TCP to communicate with a remote agent, which must be installed on the device. To use the SUT device manager:
-* ensure TCP connectivity between the local host and the remote device: check that they are on the same network and you can ping each from the other
-* ensure the SUT agent is installed and started on the remote device
-** the SUT agent APK is built alongside Firefox for Android; just install <objdir-droid>/build/mobile/sutagent/android/sutAgentAndroid.apk
-** The agent should be configured to start automatically with your phone when it boots. To start it immediately from an adb shell execute: `am start -n com.mozilla.SUTAgentAndroid/.SUTAgentAndroid -a android.intent.action.MAIN`
-* if running tests with make, set environment variable DM_TRANS=sut and set TEST_DEVICE=<ip address of device -- displayed by SUT agent>
 == Host Builds (MOZ_HOST_BIN) ==

Mobile/Fennec/Android/Testing: Difference between revisions

Mobile/Fennec/Android/Testing (view source)

Revision as of 21:40, 27 July 2018

Navigation menu

Search