Gitiles
Code Review Sign In
gerrit.openfyde.cn / chromium.googlesource.com / chromiumos / platform / tauto / refs/heads/factory-14162.B
commit3d743402e88f884fc5e0b484e699614a7f1bbe4a[log] [tgz]
authorDerek Beckett <dbeckett@chromium.org>Wed Aug 04 09:25:44 2021 -0700
committerDerek Beckett <dbeckett@chromium.org>Thu Aug 05 21:31:43 2021 +0000
treeac306ea52b1909504fc0852a642f3ea6f8eba98a
parent3c5368c3173b798dba967d8f23edc19a24e67520 [diff]
tauto rm server/hosts/*_repair*

BUG=b:192594749
TEST=dummy_Pass

Change-Id: Ia3b353dc2f50ff8e0fa06aed90cd5320f3634b8b
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/tauto/+/3071898
Tested-by: Derek Beckett <dbeckett@chromium.org>
Reviewed-by: C Shapiro <shapiroc@chromium.org>
10 files changed
tree: ac306ea52b1909504fc0852a642f3ea6f8eba98a
  1. client/
  2. docs/
  3. logs/
  4. server/
  5. site_utils/
  6. test_suites/
  7. utils/
  8. venv/
  9. autotest_lib ⇨ .
  10. MODULE_LICENSE_LGPL ⇨ LGPL_LICENSE
  11. .gitignore
  12. .style.yapf
  13. __init__.py
  14. common.py
  15. global_config.ini
  16. LGPL_LICENSE
  17. LICENSE
  18. OWNERS
  19. PRESUBMIT.cfg
  20. PRESUBMIT.py
  21. README.md
  22. 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:

Run some tauto tests

TODO: formalize/finish this.

Currently, Tauto only has 1 test to verify basic test-harness stability. This test is a client side test, dummy_Pass. There are no server side tests (yet).

To work in Tauto, the only requirement is a reasonably up-to-date chroot, and a working dut (test build) on a network your chroot can ssh with (lab network).

To run a test:

(inside)
cd ~/trunk/src/platform/tauto/
export tauto_dir=$(pwd)
cd site_utils
ssh-agent python3 test_that.py <DUT IP> dummy_Pass --autotest_dir=${tauto_dir} --py_version=3

Note: There is a TODO to clean this up to a cleaner cmd, but for now it should work.

If this works, you should see something like this:

---------------------------------------------------------------------------
/tmp/test_that_results_ib6w8qq6/results-1-dummy_Pass            [  PASSED  ]
/tmp/test_that_results_ib6w8qq6/results-1-dummy_Pass/dummy_Pass [  PASSED  ]
---------------------------------------------------------------------------
Total PASS: 2/2 (100%)

Note2: For some TBD reason, this test is a little slower than it should be, but after the first run, all subsiquent should be <20 seconds or so.

Write some tauto tests

TODO

Grabbing the latest source

TODO

Hacking and submitting patches

See the coding style guide for guidance on submitting patches.

Coding Style

Pre-upload hook dependencies

TODO

Checking in code

Right now its not expected that all the Tauto unittest's work (this note will be removed when they do). Thus, running those prior to checkin is not expected. However, the dummy_Pass test must work in python 3 prior to a checkin. Please do not check in without running this test. It only takes ~10-20 seconds, and saves lots of headache of a harness breaking, as there is no CQ-coverage ATM. Additionally, as there no CQ coverage, once you get an OWNER +2, just submit.