| 973bf71c591d2811ecaf4b8b64f6eec1ddce6bc9 |
|
26-May-2016 |
Simran Basi <sbasi@google.com> |
test_droid.py: Support passing in fastboot serials.
Some devices may have a different adb/fastboot serial.
Allow test_droid users to supply the fastboot serial.
While this allows importing multiple fastboot serials,
the work to support testbeds is not yet ready.
BUG=None
TEST=quick test on test_droid.py
Change-Id: I2625f0b48076d33369630a33830e96b35e4cda5e
Reviewed-on: https://chromium-review.googlesource.com/347606
Commit-Ready: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Kevin Cheng <kevcheng@chromium.org>
Reviewed-by: Dan Shi <dshi@google.com>
/external/autotest/site_utils/test_droid.py
|
| 5d7a7098589fe52703cda3788ce889588c42e7e4 |
|
23-Feb-2016 |
Mike Frysinger <vapier@chromium.org> |
test_droid: make serial # optional
Users need not specify the serial # by default when they only have one
device attached.
This also fixes the serial number parser to allow dashes as this shows
up in the emulator:
emulator-5554 device
BUG=b:27301538
TEST=read the doc
TEST=`./test_droid.py brillo_Gtests` works w/emu (auto-detected)
TEST=`./test_droid.py brillo_Gtests -s emulator-5554` works w/emu
TEST=`./test_droid.py brillo_Gtests -s alsdkjf` fails as it can't find device
Change-Id: I3b64fe898beea5222c64074b3ffee2e86f10eecf
Reviewed-on: https://chromium-review.googlesource.com/329140
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/site_utils/test_droid.py
|
| 57740ca3b8ceb4bf4ff682e7fe8f208d4f7357d9 |
|
19-Feb-2016 |
Simran Basi <sbasi@google.com> |
[autotest] fix test_{droid,that} --pretend.
BUG=b:27043786,chromium:586833
TEST=test_that and test_droid runs.
Change-Id: I0de93498e3d05db8bd30753d166bf7b7e7e3f486
Reviewed-on: https://chromium-review.googlesource.com/328713
Commit-Ready: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
Reviewed-by: Kevin Cheng <kevcheng@chromium.org>
/external/autotest/site_utils/test_droid.py
|
| a97d180703eab25b1dd0a8d0fb01d5d320487975 |
|
28-Jan-2016 |
Gilad Arnold <garnold@google.com> |
Tester feedback: enable interactive tests via test_droid.
This adds an --interactive option instructing interactive tests to
collect feedback from a human tester.
BUG=b:26770115
TEST=test_droid -i <dut-serial> brillo_OpenSLESPlaybackAudioTest
Change-Id: Idae365b182e621ace3e51848e8cc5287bd06e096
Reviewed-on: https://chromium-review.googlesource.com/324534
Commit-Ready: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Gilad Arnold <garnold@chromium.org>
/external/autotest/site_utils/test_droid.py
|
| f067d9c7e8dc08426a16edc89d2d33f17646a50f |
|
22-Dec-2015 |
Simran Basi <sbasi@google.com> |
test_droid: Basic remote support.
Allows test_droid to run tests against Android devices connected
to a remote host. This is useful if the test station is in the
lab and unaccesible.
BUG=b:26186193
TEST=test_droid.py ZX1G22JHXN android_DummyTest --debug \
--remote android1758-wifi-test-station-2.cros
Change-Id: I7f98440540fcf2e81e8715b81591c1d64ac60f7a
Reviewed-on: https://chromium-review.googlesource.com/319811
Commit-Ready: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Dan Shi <dshi@chromium.org>
/external/autotest/site_utils/test_droid.py
|
| 519624e8c87c5a638199da169c311441e5f7ef53 |
|
07-Dec-2015 |
Christopher Wiley <wiley@google.com> |
Use autotest's generate_test_report in test_that
Update generate_test report to conform to style and fix
broken imports from chromite/
BUG=b:25929635
TEST=`test_that dummy_Pass` passes.
Change-Id: I9a58eb2dbd773a1e3f88fafaacee289c130d29f8
Reviewed-on: https://chromium-review.googlesource.com/316524
Commit-Ready: Christopher Wiley <wiley@chromium.org>
Tested-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/site_utils/test_droid.py
|
| 1912511547a2b93ee97c3f89ebb74acd4f84cc0b |
|
16-Dec-2015 |
Christopher Wiley <wiley@google.com> |
Make test_droid import external packages before other autotest imports
Unpredicable parts of the autotest codebase depend on django/chromite.
Make sure these dependencies exists before trying to do anything else
in autotest.
BUG=None
TEST=test_droid no longer fails while importing other modules.
Change-Id: Iae6b06ac72f42e67dcb4cf24527e45ef18d0b4ba
Reviewed-on: https://chromium-review.googlesource.com/318832
Commit-Ready: Christopher Wiley <wiley@chromium.org>
Tested-by: Christopher Wiley <wiley@chromium.org>
Reviewed-by: Simran Basi <sbasi@chromium.org>
/external/autotest/site_utils/test_droid.py
|
| 14622bb8249c2200e5258ea6d40b3362229e90a7 |
|
25-Nov-2015 |
Simran Basi <sbasi@google.com> |
[autotest] test_droid V1.
This CL introduces test_droid, a script to launch autotest
tests against local Android DUTs connected to the host
computer via USB.
Much of the logic is similar to test_that, so this has all
been pulled into a new script test_utils.py
Pending work:
* Moving of generate_test_report to somewhere it is accesible
outside of the chroot.
* Add in support for remote adb hosts (i.e. the DUT is
connected to a remote computer).
* Sequences support.
BUG=b:25748759
TEST=./test_droid.py 7d52318 brillo_WhitelistedGtests
CQ-DEPEND=CL:315230
Change-Id: Idab3805f7921173fbc706354b322f37244240fa2
Reviewed-on: https://chromium-review.googlesource.com/314870
Commit-Ready: Simran Basi <sbasi@chromium.org>
Tested-by: Simran Basi <sbasi@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
/external/autotest/site_utils/test_droid.py
|