--remoteTestRoot=<remote-directory>
== talos ==
*NOTE: Talos will be retired and replaced by new tests on autophone before the end of Q2 2016.
*NOTE: this requires a fix for {{bug|1122701}}
*NOTE: this requires python 2.7
See also https://wiki.mozilla.org/Buildbot/Talos
hg clone http://hg.mozilla.org/build/talos talos
cd talos
python INSTALL.py
. bin/activate
cd talos
<obtain your fennec apk and put it in the current directory>
<obtain your robocop apk and put it in the current directory>
<obtain your fennec_ids.txt and put it in the current directory>
<install your fennec apk>
<if running a robocop-based test, install robocop.apk>
<start sutagent on the device>
python remotePerfConfigurator.py --apkPath=fennec-38.0a1.en-US.android-arm.apk
-v -e org.mozilla.fennec
--webServer=<your local desktop IP>:8080
--noChrome
--remoteDevice=<sutagent-IP>
--sampleConfig=remote.config --output=local.yml --browserWait=60
--activeTests=tcheck2
--fennecIDs=fennec_ids.txt
python run_tests.py --apkPath=fennec-38.0a1.en-US.android-arm.apk --noisy local.yml
For Robocop based tests (tcheck2, tprovider, etc...), we need to use the --fennecIDs flag to pass in the generated fennec_ids.txt file from the build you are testing. This file is generated during build time and has to match the fennec.apk and robocop.apk file. When this flag is used, we copy fennec_ids.txt and robotium.config (generated during configuration time) to the device and use those to run Robocop. If you are running ts, tp4, tsvg, or other traditional talos tests, there is no need for the --fennecIDs flag.
Aside: For a quick-and-dirty hacky way to run robocop-talos tests locally, see [[Mobile/Fennec/Android/LocalRoboTalos]]
== S1/S2 Automation ==
