Lines Matching +full:- +full:- +full:no +full:- +full:commit +full:- +full:id
5 [Autotest Best Practices](best-practices.md)
7 [test\_that Basic Usage](test-that.md)
46 $ ./site_utils/test_droid.py suite:brillo-bvt
63 $ ./site_utils/test_droid.py -s 7d52318 brillo_WhitelistedGtests
74 emulator-5554 device
77 $ ./site_utils/test_droid.py -s emulator-5554,7d52318 testbed_DummyTest
83 If no username is specified, `test_droid` will try the root and adb users.
90 …e OS testing keys](https://www.chromium.org/chromium-os/testing/autotest-developer-faq/ssh-test-ke…
97 CheckHostIP no
98 StrictHostKeyChecking no
107 -r <Remote Server IP or Hostname> \
111 -r <User>@<Remote Server IP or Hostname> \
114 $ ./site_utils/test_droid.py -r 100.96.48.119 suite:brillo-bvt
118 Currently Autotest in AOSP is read-only, so you cannot use repo upload to
119 upload code changes. If you do edit or add a new test, make a commit and upload
120 it to https://chromium-review.googlesource.com.
124 contain the merge commits. It will also reject the automerge committer ID.
125 To work around this, if you need to upload a commit to Autotest, you first have
129 $ git remote add -t master cros \
133 $ git checkout -b <local branch name>
134 $ git branch --set-upstream-to=cros/master
146 $ utils/build_externals.py # install any missing os packages with apt-get
150 Then upload your commit for review:
159 to server-side tests, which run on an autotest server and control a
164 `test_droid` does not support the autoupdate end-to-end test. For instructions
166 End-to-End Test doc.