commit | d8e1a28b0ea211466398a221a7351a10cbfd5910 | [log] [tgz] |
---|---|---|
author | Sandro <sandrom@google.com> | Thu Mar 02 13:51:18 2023 +0000 |
committer | Sandro Montanari <sandrom@google.com> | Fri Mar 03 15:35:45 2023 +0000 |
tree | 5790fe5a1a1055f21c16807116fa85650620cc67 | |
parent | 099fb10bf432a7f7fb846b5aca20dac89ff5e6b5 [diff] |
Add parameter to instrument tests for running sdk-in-sandbox Sandbox-instrumented tests should allow two possible modes, either (1) running the whole test as a sandbox, or (2) running a test as an sdk inside the sandbox. Currently only mode (1) is supported. This CL introduces an instrumentation parameter to support case (2). Bug: 271270588 Test: I tested the two modes as follows: mode (1): atest CtsSdkSandboxInprocessTests mode (2): atest CtsSensorRatePermissionTestCases -- --enable-optional-parameterization --enable-parameterized-modules --module-parameter run_on_sdk_sandbox Change-Id: I29a0f6f252cc04ad7099193c09e9db6cba4698d7
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.