| commit | f9c6aebcaf988461669dd9f04b6aca51dab6ee9c | [log] [tgz] |
|---|---|---|
| author | Abhijeet Kaur <abkaur@google.com> | Wed Jan 22 18:15:49 2020 +0000 |
| committer | Abhijeet Kaur <abkaur@google.com> | Wed Jan 29 19:01:43 2020 +0000 |
| tree | 289bd74c8971cf6c3e38142c09acd871b54604f4 | |
| parent | e6c1b1cd490310c43dfb95c566d2858bcdb4584f [diff] |
Grant legacy storage access to the test apps that request for it Apps requesting full (legacy) external storage will only be allowed legacy external storage if the app is targeting Q or lower. Many CTS test apps (that are not testing storage workflow) are violating the new Scoped Storage resctrictions (around direct file path access) added by Android Storage team for R. Since most of these CTS test apps target sdkcurrent (which is > Q) so these cts tests will fail as we are enforcing storage restrictions in R and apps cannot opt out of it. This change allows legacy external storage for test apps (that request for it) by giving them File Manager permissions (which have full external storage access). Bug: 142395442 Test: atest CtsDownloadManagerLegacy Test: atest android.appsecurity.cts.ExternalStorageHostTest#testMultiUserStorageIsolated Test: atest android.os.cts.FileAccessPermissionTest#testExternalStorageAccess Change-Id: I45d37d3d0d2202e3670eb86519f2ce31d23dd662
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.
Building TF:
More information at: https://source.android.com/devices/tech/test_infra/tradefed/
See more details about Tradefed Architecture at: https://source.android.com/devices/tech/test_infra/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.