Google Git
Sign in
cos / mirrors / cros / chromiumos / third_party / autotest / 5e58911f5bec4c19da945bdfa157c2f88cf608d4
commit5e58911f5bec4c19da945bdfa157c2f88cf608d4[log] [tgz]
authorDerek Beckett <dbeckett@chromium.org>Wed May 05 17:22:02 2021 +0000
committerDerek Beckett <dbeckett@chromium.org>Wed May 05 17:23:26 2021 +0000
treec32ade83304ba641134f27db722398960733f82d
parent9dfa25f5c93c1b59b1ffd79a9ed4e00a8b8076dc [diff]
Revert "Update autoupdate_ForcedOOBEUpdate to use FakeOmaha."

This reverts commit e1c90bb3c62a8b182dc33f97e51e7baf54e56a50.

Reason for revert: import is invalid on r90. breaks unittest

Original change's description:
> Update autoupdate_ForcedOOBEUpdate to use FakeOmaha.
>
> I'll trial the TLS change with this test before migrating them all.
> I cannot run the test locally with TLS so we will have to test in the
> lab. I have verified that it runs and fails at the same point as the
> infra_TLSFakeOmaha test.
>
> BUG=chromium:1189379
> TEST=autoupdate_ForcedOOBEUpdate and fails with same error as
> infra_TLSFakeOmaha
>
> Change-Id: I9f8782a213a719d2d7a29737462ff05a025f2648
> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2815950
> Tested-by: David Haddock <dhaddock@chromium.org>
> Reviewed-by: Derek Beckett <dbeckett@chromium.org>
> Reviewed-by: Kyle Shimabukuro <kyleshima@chromium.org>
> (cherry picked from commit fb17b1a9a412f3e8037988f9c75b4314e80b9b37)
> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2861669
> Reviewed-by: David Haddock <dhaddock@chromium.org>
> Commit-Queue: David Haddock <dhaddock@chromium.org>

Bug: chromium:1189379
Change-Id: Id9bb788c09fce7c765b6405ae7ca6ba6662e74a2
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/2875371
Auto-Submit: Derek Beckett <dbeckett@chromium.org>
Reviewed-by: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Commit-Queue: Abhishek Pandit-Subedi <abhishekpandit@chromium.org>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
2 files changed
tree: c32ade83304ba641134f27db722398960733f82d
  1. bin/
  2. cli/
  3. client/
  4. contrib/
  5. database/
  6. docs/
  7. frontend/
  8. logs/
  9. metadata/
  10. results/
  11. server/
  12. site_utils/
  13. test_suites/
  14. tko/
  15. utils/
  16. venv/
  17. autotest_lib ⇨ .
  18. MODULE_LICENSE_LGPL ⇨ LGPL_LICENSE
  19. .gitignore
  20. .style.yapf
  21. __init__.py
  22. common.py
  23. CTS_OWNERS
  24. ENGPROD_OWNERS
  25. FINGERPRINT_OWNERS
  26. FIRMWARE_OWNERS
  27. global_config.ini
  28. INFRA_OWNERS
  29. LGPL_LICENSE
  30. LICENSE
  31. main.star
  32. moblab_config.ini
  33. PRESUBMIT.cfg
  34. PRESUBMIT.py
  35. README.md
  36. ssp_deploy_config.json
  37. unblocked_terms.txt
README.md

Autotest: Automated integration testing for Android and Chrome OS Devices

Autotest is a framework for fully automated testing. It was originally designed to test the Linux kernel, and expanded by the Chrome OS team to validate complete system images of Chrome OS and Android.

Autotest is composed of a number of modules that will help you to do stand alone tests or setup a fully automated test grid, depending on what you are up to. A non extensive list of functionality is:

  • A body of code to run tests on the device under test. In this setup, test logic executes on the machine being tested, and results are written to files for later collection from a development machine or lab infrastructure.

  • A body of code to run tests against a remote device under test. In this setup, test logic executes on a development machine or piece of lab infrastructure, and the device under test is controlled remotely via SSH/adb/some combination of the above.

  • Developer tools to execute one or more tests. test_that for Chrome OS and test_droid for Android allow developers to run tests against a device connected to their development machine on their desk. These tools are written so that the same test logic that runs in the lab will run at their desk, reducing the number of configurations under which tests are run.

  • Lab infrastructure to automate the running of tests. This infrastructure is capable of managing and running tests against thousands of devices in various lab environments. This includes code for both synchronous and asynchronous scheduling of tests. Tests are run against this hardware daily to validate every build of Chrome OS.

  • Infrastructure to set up miniature replicas of a full lab. A full lab does entail a certain amount of administrative work which isn't appropriate for a work group interested in automated tests against a small set of devices. Since this scale is common during device bringup, a special setup, called Moblab, allows a natural progressing from desk -> mini lab -> full lab.

Run some autotests

See the guides to test_that and test_droid:

test_droid Basic Usage

test_that Basic Usage

Write some autotests

See the best practices guide, existing tests, and comments in the code.

Autotest Best Practices

Grabbing the latest source

git clone https://chromium.googlesource.com/chromiumos/third_party/autotest

Hacking and submitting patches

See the coding style guide for guidance on submitting patches.

Coding Style

Pre-upload hook dependencies

You need to run utils/build_externals.py to set up the dependencies for pre-upload hook tests.

Setting up Lucifer

Setting up Lucifer