Autoupdate tests should wait for Android to boot after updating |
|||
Issue descriptionThe autoupdate_EndToEnd autotests use login_LoginSuccess (before and) after an update to check that for a successful update. On ARC++ devices, we should also check that Android boots up. This will remove a lot of manual checking by the test team I have a CL to do this
,
Jul 21 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 21 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/0c88356d674fbc2545000483603ea3bdb9d13529 commit 0c88356d674fbc2545000483603ea3bdb9d13529 Author: David Haddock <dhaddock@chromium.org> Date: Wed Jul 20 19:32:24 2016 Make the autoupdate tests wait for Android to boot after updating. We should let the autoupdate tests ensure that we can login AND start Android after an autoupdate. This will remove a lot of manual checking needed by the test team. BUG= chromium:629929 TEST=test_that <ip> --args="name=npo update_type=full source_release=8530.20.0 target_release=8530.21.0 target_payload_uri=gs://chromeos-image-archive/<path>" autoupdate_EndToEndTest Change-Id: I1eb0d37f9faba5163963e17d2b3630f40b142558 Reviewed-on: https://chromium-review.googlesource.com/361963 Commit-Ready: David Haddock <dhaddock@chromium.org> Tested-by: David Haddock <dhaddock@chromium.org> Reviewed-by: David Haddock <dhaddock@chromium.org> [modify] https://crrev.com/0c88356d674fbc2545000483603ea3bdb9d13529/client/site_tests/login_LoginSuccess/login_LoginSuccess.py [modify] https://crrev.com/0c88356d674fbc2545000483603ea3bdb9d13529/server/site_tests/autoupdate_EndToEndTest/autoupdate_EndToEndTest.py
,
Jul 25 2016
AU is still green after the change. |
|||
►
Sign in to add a comment |
|||
Comment 1 by dhadd...@chromium.org
, Jul 20 2016