| /tools/platform-compat/javatest/com/android/class2nonsdklist/ |
| D | UnsupportedAppUsageAnnotationHandlerTest.java | 60 mJavac.addSource("annotation.Anno", Joiner.on('\n').join( in setup()
87 mJavac.addSource("a.b.Class", Joiner.on('\n').join( in testGreylistMethod()
108 mJavac.addSource("a.b.Class", Joiner.on('\n').join( in testGreylistConstructor()
129 mJavac.addSource("a.b.Class", Joiner.on('\n').join( in testGreylistField()
150 mJavac.addSource("a.b.EnumClass", Joiner.on('\n').join( in testGreylistImplicit()
171 mJavac.addSource("a.b.EnumClass", Joiner.on('\n').join( in testGreylistImplicit_Invalid_MissingOnClass()
193 mJavac.addSource("a.b.EnumClass", Joiner.on('\n').join( in testGreylistImplicit_Invalid_PresentOnMember()
214 mJavac.addSource("a.b.Class", Joiner.on('\n').join( in testGreylistMethodExpectedSignature()
235 mJavac.addSource("a.b.Class", Joiner.on('\n').join( in testGreylistMethodExpectedSignatureWrong()
253 mJavac.addSource("a.b.Class", Joiner.on('\n').join( in testGreylistInnerClassMethod()
[all …]
|
| D | CovariantReturnTypeHandlerTest.java | 54 mJavac.addSource("annotation.Annotation", Joiner.on('\n').join( in setup()
66 mJavac.addSource("a.b.Class", Joiner.on('\n').join( in testReturnTypeWhitelisted()
90 mJavac.addSource("a.b.Class", Joiner.on('\n').join( in testAnnotatedMemberNotPublicApi()
112 mJavac.addSource("a.b.Class", Joiner.on('\n').join( in testReturnTypeAlreadyWhitelisted()
137 mJavac.addSource("a.b.Class", Joiner.on('\n').join( in testAnnotationOnField()
|
| /tools/asuite/atest-py2/docs/ |
| D | developer_workflow.md | 6 1. [Identify the code you should work on](#identify-the-code-you-should-work-on)
7 2. [Working on the Python Code](#working-on-the-python-code)
8 3. [Working on the TradeFed Code](#working-on-the-tradefed-code)
9 4. [Working on the VTS10-TradeFed Code](#working-on-the-vts10-tradefed-code)
10 5. [Working on the Robolectric Code](#working-on-the-robolectric-code)
13 ## <a name="what-code">Identify the code you should work on</a>
30 code you'll want to work on.
32 <p>For more details on how this code works, checkout the following docs:
51 ## <a name="working-on-the-python-code">Working on the Python Code</a>
78 ## <a name="working-on-the-tradefed-code">Working on the TradeFed Code</a>
[all …]
|
| D | atest_structure.md | 19 2. Find test(s) based on user input
29 it). That is a critical piece that atest depends on. Module-info.json contains a
51 Read on to learn more about the classes mentioned.
62 * ```test_finders/``` - Location of test finder classes. More details on test
68 * ```test_runners/``` - Location of test runner classes. More details on test
76 atest to find tests in the android repo based on the user's input (path,
81 For more details and instructions on how to create new test finders,
89 For more details and instructions on how to create new test runners, [go here](./develop_test_runne…
|
| /tools/asuite/atest/docs/ |
| D | developer_workflow.md | 6 1. [Identify the code you should work on](#identify-the-code-you-should-work-on)
7 2. [Working on the Python Code](#working-on-the-python-code)
8 3. [Working on the TradeFed Code](#working-on-the-tradefed-code)
9 4. [Working on the VTS10-TradeFed Code](#working-on-the-vts10-tradefed-code)
10 5. [Working on the Robolectric Code](#working-on-the-robolectric-code)
13 ## <a name="what-code">Identify the code you should work on</a>
30 code you'll want to work on.
32 <p>For more details on how this code works, checkout the following docs:
51 ## <a name="working-on-the-python-code">Working on the Python Code</a>
78 ## <a name="working-on-the-tradefed-code">Working on the TradeFed Code</a>
[all …]
|
| D | atest_structure.md | 19 2. Find test(s) based on user input
29 it). That is a critical piece that atest depends on. Module-info.json contains a
51 Read on to learn more about the classes mentioned.
62 * ```test_finders/``` - Location of test finder classes. More details on test
68 * ```test_runners/``` - Location of test runner classes. More details on test
76 atest to find tests in the android repo based on the user's input (path,
81 For more details and instructions on how to create new test finders,
89 For more details and instructions on how to create new test runners, [go here](./develop_test_runne…
|
| /tools/apksig/src/apksigner/java/com/android/apksigner/ |
| D | help_verify.txt | 3 This checks whether the provided APK will verify on Android. By default, this
4 checks whether the APK will verify on all Android platform versions supported
16 --min-sdk-version Lowest API Level on which this APK's signatures will be
20 --max-sdk-version Highest API Level on which this APK's signatures will be
33 1. Check whether the APK's signatures are expected to verify on all Android
37 2. Check whether the APK's signatures are expected to verify on Android
|
| D | help_sign.txt | 24 signing using this scheme is enabled based on min and max
30 enabled based on min and max SDK version (see
36 enabled based on min and max SDK version (see
41 an appropriate signer on all supported platform versions.
46 enabled based on min and max SDK version (see
56 --min-sdk-version Lowest API Level on which this APK's signatures will be
61 --max-sdk-version Highest API Level on which this APK's signatures will be
86 points in the lineage and will be used on older platform
143 stdin password provided on standard input,
162 stdin password provided on standard input,
[all …]
|
| D | help.txt | 10 signatures of APK files will verify on Android devices.
18 verify Check whether the provided APK is expected to verify on
|
| /tools/test/connectivity/acts_tests/acts_contrib/test_utils/gnss/ |
| D | gnss_testlog_utils.py | 289 lambda item1, item2: pds.merge(item1, item2, on='time_row_num'), [
296 on='time_row_num')
302 lambda item1, item2: pds.merge(item1, item2, on='time_row_num'), [
309 on='time_row_num')
375 lambda item1, item2: pds.merge(item1, item2, on='phone_time'),
380 on='phone_time')
386 lambda item1, item2: pds.merge(item1, item2, on='phone_time'),
391 on='phone_time')
396 lambda item1, item2: pds.merge(item1, item2, on='phone_time'),
401 on='phone_time')
|
| /tools/ndkports/src/test/kotlin/com/android/ndkports/ |
| D | ResultTest.kt | 25 fun `onFailure executes block on failure`() { in onFailure executes block on failure()
35 fun `onFailure does not execute block on success`() { in onFailure does not execute block on success()
47 fun `onSuccess executes block on success`() { in onSuccess executes block on success()
57 fun `onSuccess does not execute block on failure`() { in onSuccess does not execute block on failure()
|
| /tools/test/openhst/ |
| D | README.md | 4 performance on Android devices with simple test set up. The goal of OpenHST is
6 Partners can easily adapt on their development.
17 * DSP hotword capability on test device (android handset)
19 * Internet connection on android handset
20 * No screen lock setting on android handset
23 * Install GNU make(3.81 above) on test machine (Linux, Mac, Windows)
27 Please follow below steps to set up HST on your test machine and make sure that
|
| D | stress_test.proto | 11 * distributed under the License is distributed on an "AS IS" BASIS,
24 // The process name that this event can be found on, or LOGCAT to come from
47 // The multiplier used on the parsed monotonic time to convert it to seconds.
52 // The file that should be cat-ed on device to get information. Will be used
55 // The filepath to save the output of this file on the local machine. If
70 // The filepath to save the output of this process on the local machine. If
96 // on the name), only the "latest" in the include chain will be used.
116 // Command to run on this test step.
155 // Events that trigger special actions on the device when the condition is
|
| D | LICENSE | 42 form, that is based on (or derived from) the Work and for which the
53 or by an individual or Legal Entity authorized to submit on behalf of
57 communication on electronic mailing lists, source code control systems,
58 and issue tracking systems that are managed by, or on behalf of, the
64 on behalf of whom a Contribution has been received by Licensor and
146 Contributor provides its Contributions) on an "AS IS" BASIS,
171 on Your own behalf and on Your sole responsibility, not on behalf
186 file or class name and description of purpose be included on the
199 distributed under the License is distributed on an "AS IS" BASIS,
|
| /tools/test/connectivity/acts_tests/tests/google/bt/pts/instructions/ |
| D | GAP_PTS_INSTRUCTIONS | 10 # distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
198 Note: Do not accept pairing on phone until after you accept it on PTS
228 Note: Do not accept pairing on phone until after you accept it on PTS
242 [PTS Interaction] Enter PIN from PTS to phone (hit ok on phone before PTSbt )
275 Do not accept pairing on phone until after you accept it on PTS
311 Note: Do not accept pairing on phone until after you accept it on PTS
371 Accept Pairing on Phone (check contacts box)
384 [PTS Interaction] Select ok on PTS
529 Note: Run these commands before executing the testcase on PTS Side
537 Note: Run these commands before executing the testcase on PTS Side
[all …]
|
| /tools/carrier_settings/ |
| D | README | 15 This tool is best supported on Android 11 code base. See additional steps
16 in bin/README.md run it on Android 10.
19 based on MCC/MNC values. However, a CarrierConfig carriersettingstool.no_apn_for_mvno_bool
|
| /tools/repohooks/ |
| D | README.md | 4 perform various checks automatically such as running linters on your code.
7 turn on any hook it wishes to enforce.
33 the local project you're working on.
48 settings on top.
105 * `${PREUPLOAD_FILES}`: List of files to operate on.
106 * `${PREUPLOAD_FILES_PREFIXED}`: A list of files to operate on.
141 * `ignore_merged_commits`: If set to `true`, the hooks will not run on commits
142 that are merged. Hooks will still run on the merge commit itself.
146 This section allows for completely arbitrary hooks to run on a per-repo basis.
170 This section allows for turning on common/builtin hooks. There are a bunch of
[all …]
|
| /tools/external/fat32lib/ |
| D | NOTICE | 17 …Public License is the better strategy to use in any particular case, based on the explanations bel…
27 … free library. Also, if the library is modified by someone else and passed on, the recipients shou…
37 For example, on rare occasions, there may be a special need to encourage the widest possible use of…
43 …cation follow. Pay close attention to the difference between a "work based on the library" and a "…
51 …ibrary or work which has been distributed under these terms. A "work based on the Library" means e…
55 …titute a work based on the Library (independent of the use of the Library in a tool for writing it…
57 …, in any medium, provided that you conspicuously and appropriately publish on each copy an appropr…
61 …y or copies of the Library or any portion of it, thus forming a work based on the Library, and cop…
69 …ctions as part of a whole which is a work based on the Library, the distribution of the whole must…
71 …rcise the right to control the distribution of derivative or collective works based on the Library.
[all …]
|
| /tools/apksig/ |
| D | LICENSE | 8 distributed under the License is distributed on an "AS IS" BASIS,
54 form, that is based on (or derived from) the Work and for which the
65 or by an individual or Legal Entity authorized to submit on behalf of
69 communication on electronic mailing lists, source code control systems,
70 and issue tracking systems that are managed by, or on behalf of, the
76 on behalf of whom a Contribution has been received by Licensor and
158 Contributor provides its Contributions) on an "AS IS" BASIS,
183 on Your own behalf and on Your sole responsibility, not on behalf
198 file or class name and description of purpose be included on the
211 distributed under the License is distributed on an "AS IS" BASIS,
|
| /tools/security/ |
| D | OWNERS | 1 # Code owners for various security-related things on Android.
7 # Haiku members (fuzzing-on-Android)
|
| /tools/test/connectivity/acts_tests/tests/google/fuchsia/bt/pts/ |
| D | GATT_PTS_INSTRUCTIONS | 10 # distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
73 [Fuchsia interaction] Type 'y' on the bt-pairing-tool
96 [Fuchsia interaction] Type 'y' on the bt-pairing-tool
119 [Fuchsia interaction] Type 'y' on the bt-pairing-tool
162 [Fuchsia interaction] Type 'y' on the bt-pairing-tool
194 Fuchsia interaction] Type 'y' on the bt-pairing-tool
|
| /tools/treble/ |
| D | LICENSE | 42 form, that is based on (or derived from) the Work and for which the
53 or by an individual or Legal Entity authorized to submit on behalf of
57 communication on electronic mailing lists, source code control systems,
58 and issue tracking systems that are managed by, or on behalf of, the
64 on behalf of whom a Contribution has been received by Licensor and
146 Contributor provides its Contributions) on an "AS IS" BASIS,
171 on Your own behalf and on Your sole responsibility, not on behalf
186 file or class name and description of purpose be included on the
199 distributed under the License is distributed on an "AS IS" BASIS,
|
| /tools/acloud/ |
| D | LICENSE | 42 form, that is based on (or derived from) the Work and for which the
53 or by an individual or Legal Entity authorized to submit on behalf of
57 communication on electronic mailing lists, source code control systems,
58 and issue tracking systems that are managed by, or on behalf of, the
64 on behalf of whom a Contribution has been received by Licensor and
146 Contributor provides its Contributions) on an "AS IS" BASIS,
171 on Your own behalf and on Your sole responsibility, not on behalf
186 file or class name and description of purpose be included on the
199 distributed under the License is distributed on an "AS IS" BASIS,
|
| /tools/trebuchet/ |
| D | LICENSE | 42 form, that is based on (or derived from) the Work and for which the
53 or by an individual or Legal Entity authorized to submit on behalf of
57 communication on electronic mailing lists, source code control systems,
58 and issue tracking systems that are managed by, or on behalf of, the
64 on behalf of whom a Contribution has been received by Licensor and
146 Contributor provides its Contributions) on an "AS IS" BASIS,
171 on Your own behalf and on Your sole responsibility, not on behalf
186 file or class name and description of purpose be included on the
199 distributed under the License is distributed on an "AS IS" BASIS,
|
| /tools/security/sanitizer-status/ |
| D | NOTICE | 8 distributed under the License is distributed on an "AS IS" BASIS,
54 form, that is based on (or derived from) the Work and for which the
65 or by an individual or Legal Entity authorized to submit on behalf of
69 communication on electronic mailing lists, source code control systems,
70 and issue tracking systems that are managed by, or on behalf of, the
76 on behalf of whom a Contribution has been received by Licensor and
158 Contributor provides its Contributions) on an "AS IS" BASIS,
183 on Your own behalf and on Your sole responsibility, not on behalf
|