| commit | b04d9af888a506f6949f4d1959358090f7a82e72 | [log] [tgz] |
|---|---|---|
| author | Frederick Mayle <fmayle@google.com> | Tue Apr 02 13:22:25 2024 -0700 |
| committer | Frederick Mayle <fmayle@google.com> | Wed Apr 03 20:15:37 2024 +0000 |
| tree | 0036697f42a474b017073b5d14a886707859fabb | |
| parent | bb67948841c8ae359e6098a612caa6dca5f3cbcc [diff] |
return error when device type doesn't support snapshotting The non-error response text is essentially ignored, so this would silently fail. Made the try-catch narrower so that basic coding errors like null deref exceptions are easier to debug. Test: `atest SnapshotTest` on a dev machine Change-Id: Ifa88d58650fe629a8323b236c868a9eb1b11184e
TF is a test harness used to drive Android automated testing. It runs on test hosts and monitors the connected devices, handling test scheduling & execution and device management.
Other test harnesses like Compatibility Test Suite (CTS) and Vendor Test Suite (VTS) use TF as a basis and extend it for their particular needs.
1. Create your change in Gerrit 2. Add the reviewer named "Tradefed Codereview" (email: tradefed-codereview@tradefederation.google.com.iam.gserviceaccount.com) 3. Review the code review guidance at go/tf-guidelines and go/tradefed-code-reviews 4. GWSQ should add a couple of people from the team to review your code and give feedback.
More information at: https://source.android.com/docs/core/tests/tradefed/
See more details about Tradefed Architecture at: https://source.android.com/docs/core/tests/tradefed/architecture
If you are a tests writer you should start looking in the test_framework/ component which contains everything needed to write a tests in Tradefed.