| /tools/tradefederation/core/test_result_interfaces/com/android/tradefed/util/proto/ |
| D | TestRecordProtoUtil.java | 60 CodedInputStream is = CodedInputStream.newInstance(stream); in readFromFile() local
62 is.setSizeLimit(Integer.MAX_VALUE); in readFromFile()
64 while (!is.isAtEnd()) { in readFromFile()
65 int size = is.readRawVarint32(); in readFromFile()
66 byte[] dataByte = is.readRawBytes(size); in readFromFile()
72 record = TestRecord.parseFrom(is); in readFromFile()
|
| /tools/apksig/src/apksigner/java/com/android/apksigner/ |
| D | help_sign.txt | 4 is performed using one or more signers, each represented by an asymmetric key
5 pair and a corresponding certificate. Typically, an APK is signed by just one
12 --in Input APK file to sign. This is an alternative to
14 options. Unless --out is specified, this file will be
18 APK is signed in-place, overwriting the input file.
24 signing using this scheme is enabled based on min and max
29 API Level 24. By default, signing using this scheme is
35 API Level 28. By default, signing using this scheme is
40 "lineage" option to make sure that the app is signed by
45 API Level 30. By default, signing using this scheme is
[all …]
|
| D | help_lineage.txt | 28 This option is required for each signer to be modified in the provided SigningCertificateLineage.
41 used in some situations on the platform even though the APK is now being signed
46 this value is not specified then the option will default to true.
50 no file is needed by KeyStore, which is the case for some
66 A password is required to open a KeyStore.
69 When the same file (including standard input) is used for
73 signer, KeyStore password is read before the key password
74 is read.
76 --key-pass Password with which the private key is protected.
85 If --key-pass is not specified for a KeyStore key, this
[all …]
|
| D | help_rotate.txt | 42 used in some situations on the platform even though the APK is now being signed
47 true or false; if this value is not specified then the option will default to
53 no file is needed by KeyStore, which is the case for some
69 A password is required to open a KeyStore.
72 When the same file (including standard input) is used for
76 signer, KeyStore password is read before the key password
77 is read.
79 --key-pass Password with which the private key is protected.
88 If --key-pass is not specified for a KeyStore key, this
92 If --key-pass is not specified for a private key file key,
[all …]
|
| /tools/acloud/internal/proto/ |
| D | internal_config.proto | 10 // distributed under the License is distributed on an "AS IS" BASIS,
31 // [CVD only] The project where stable host image is
35 // [GOLDFISH only] The project where stable host image is
39 // [CHEEPS only] The project where stable host image is
74 // If file is of this type, it will be compressed to avd-system.tar.gz
77 // is greater than 0
82 // this config is valid for.
87 // the home directory if the user is authenticated via Oauth2 method.
88 // The file name by convention usually starts with a dot noting it is
91 // user_agent is a string noting which software it is.
[all …]
|
| /tools/tradefederation/core/atest/docs/ |
| D | develop_test_runners.md | 11 The test runner class is responsible for test execution. Its primary logic
14 top-level args consumed by atest passed onto the test runner. It is up to the
17 the atest CLI and your test runner's CLI. The reason for this is so that atest
25 First thing to choose is where to put the test runner. This will primarily
27 ```test_runners/``` is the default location.
41 * ```host_env_check()```: Check if host environment is properly setup for the
52 There is a parent helper method (```run```) that should be used to execute the
55 Once the test runner class is created, you'll need to add it in
56 ```test_runner_handler``` so that atest is aware of it. Try-except import the
57 test runner in ```_get_test_runners``` like how ```ExampleTestRunner``` is.
|
| D | develop_test_finders.md | 11 A test finder class holds find methods. A find method is given a string (the
22 If the metadata used to find a test is unlike existing test finder classes,
23 that is the right time to create a new class. Metadata can be anything like
30 First thing to choose is where to put the test finder. This will primarily
32 ```test_finders/``` is the default location.
48 field as a dict. Check out ```ExampleFinder``` to see how the data field is
52 This is used by the class decorator to identify the find methods of the class.
54 Final bit is to add your test finder class to ```test_finder_handler```.
|
| D | developer_workflow.md | 15 Atest is essentially a wrapper around various test runners. Because of
18 and run. Note that the wrapper code is written in python, so we'll be
24 Its job is to translate user inputs into (1) build targets and (2)
29 If your contribution involves any of this functionality, this is the
40 This is the code that actually runs the test. If your change
41 involves how the test is actually run, you'll need to work with this
86 The `testtype/suite/AtestRunner.java` is the most important file in
89 `test_runners/atest_tf_test_runner.py`. This is the file you'll want
104 TradeFed itself is used to run the TradeFed unittests so you'll need
110 command to run an individual test file is:<br>
[all …]
|
| /tools/asuite/atest/docs/ |
| D | develop_test_runners.md | 11 The test runner class is responsible for test execution. Its primary logic
14 top-level args consumed by atest passed onto the test runner. It is up to the
17 the atest CLI and your test runner's CLI. The reason for this is so that atest
25 First thing to choose is where to put the test runner. This will primarily
27 ```test_runners/``` is the default location.
41 * ```host_env_check()```: Check if host environment is properly setup for the
52 There is a parent helper method (```run```) that should be used to execute the
55 Once the test runner class is created, you'll need to add it in
56 ```test_runner_handler``` so that atest is aware of it. Try-except import the
57 test runner in ```_get_test_runners``` like how ```ExampleTestRunner``` is.
|
| D | develop_test_finders.md | 11 A test finder class holds find methods. A find method is given a string (the
22 If the metadata used to find a test is unlike existing test finder classes,
23 that is the right time to create a new class. Metadata can be anything like
30 First thing to choose is where to put the test finder. This will primarily
32 ```test_finders/``` is the default location.
48 field as a dict. Check out ```ExampleFinder``` to see how the data field is
52 This is used by the class decorator to identify the find methods of the class.
54 Final bit is to add your test finder class to ```test_finder_handler```.
|
| D | developer_workflow.md | 15 Atest is essentially a wrapper around various test runners. Because of
18 and run. Note that the wrapper code is written in python, so we'll be
24 Its job is to translate user inputs into (1) build targets and (2)
29 If your contribution involves any of this functionality, this is the
40 This is the code that actually runs the test. If your change
41 involves how the test is actually run, you'll need to work with this
86 The `testtype/suite/AtestRunner.java` is the most important file in
89 `test_runners/atest_tf_test_runner.py`. This is the file you'll want
104 TradeFed itself is used to run the TradeFed unittests so you'll need
110 command to run an individual test file is:<br>
[all …]
|
| /tools/tradefederation/core/src/com/android/tradefed/testtype/suite/ |
| D | TestSuiteInfo.java | 49 try (InputStream is = TestSuiteInfo.class.getResourceAsStream(SUITE_INFO_PROPERTY)) { in TestSuiteInfo() argument
50 if (is != null) { in TestSuiteInfo()
51 mTestSuiteInfo = loadSuiteInfo(is); in TestSuiteInfo()
72 protected Properties loadSuiteInfo(InputStream is) throws IOException { in loadSuiteInfo() argument
74 p.load(is); in loadSuiteInfo()
|
| /tools/external/fat32lib/ |
| D | NOTICE | 7 Everyone is permitted to copy and distribute verbatim copies
8 of this license document, but changing it is not allowed.
10 [This is the first released version of the Lesser GPL. It also counts
15 … your freedom to share and change free software--to make sure the software is free for all its use…
17 …arefully about whether this license or the ordinary General Public License is the better strategy …
27 … is no warranty for the free library. Also, if the library is modified by someone else and passed …
31 …is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public…
33 When a program is linked with a library, whether statically or using a shared library, the combinat…
37 …rary. A more frequent case is that a free library does the same job as widely used non-free librar…
41 … Lesser General Public License is Less protective of the users' freedom, it does ensure that the u…
[all …]
|
| /tools/tradefederation/core/tests/res/testtype/ |
| D | python_subtest_output.txt | 10 AssertionError: False is not true
18 AssertionError: False is not true
26 AssertionError: False is not true
34 AssertionError: False is not true
|
| D | gtest_output5.txt | 28 WARNING: Environment variable GTEST_TEMP is expected to be a 32-bit integer, but actually has value…
29 The default value 20 is used.
30 WARNING: Environment variable GTEST_TEMP is expected to be a 32-bit integer, but actually has value…
31 The default value 30 is used.
34 This is some random text that should get captured by the parser.
|
| /tools/trebuchet/ |
| D | README.md | 3 Trebuchet is a Kotlin library for parsing and analyzing Android trace files generated by the `atrac…
15 …nts. If Trebuchet is built using the Android build system, there will be a StartupAnalyzerKt prog…
19 …us. If Trebuchet is built using the Android build system, there will be a StartupSummarizerKt pro…
|
| /tools/apksig/ |
| D | README.md | 3 apksig is a project which aims to simplify APK signing and checking whether APK signatures are
8 Android Nougat, API Level 24). apksig is meant to be used outside of Android devices.
10 The key feature of apksig is that it knows about differences in APK signature verification logic
12 signature is expected to verify on all Android platform versions supported by the APK. When signing
28 * `ApkVerifier` which checks whether the provided APK is expected to verify on all Android
31 This is useful in optimized APK building pipelines, such as in Android Plugin for Gradle,
33 where the APK to be signed is available upfront, the `ApkSigner` above is easier to use.
|
| /tools/test/connectivity/acts/tests/google/tel/config/ |
| D | README.md | 4 …- **(\*experimental) enable_wifi_verbose_logging** - This key, if defined (the value is unused), w…
5 …is to capture a bug report after each failed test. In situations where this is overly time consumi…
6 …m_conf_file** - Path to a SIM card config file, which is needed in the event that the MSISDN/MDN i…
|
| /tools/test/connectivity/acts/framework/acts/controllers/buds_lib/dev_utils/proto/google/protobuf/ |
| D | descriptor.proto | 79 // functionality of the descriptors -- the information is needed only by
112 // 0 is reserved for errors.
113 // Order is weird for historical reasons.
141 // 0 is reserved for errors
152 // If type_name is set, this need not be set. If both this and type_name
156 // For message and enum types, this is the name of the type. If the name
157 // starts with a '.', it is fully-qualified. Otherwise, C++-like scoping
163 // For extensions, this is the name of the type being extended. It is
175 // list. This field is a member of that oneof. Extensions of a oneof should
249 // through 99999. It is up to you to ensure that you do not use the
[all …]
|
| /tools/test/connectivity/acts/ |
| D | README.md | 2 The Android Comms Test Suite, is a lightweight Python-based automation tool set
3 that is used to perform automated testing of current and upcoming Android
6 of utility functions to further ease test development. It is an ideal desktop
21 it is recommended for all new test cases.
37 Below is a high level view of the ACTS flow:
64 2. Tap Build number repeatedly until "You're a developer now" is displayed.
77 3. To verify ACTS is ready to go, at the location for README, and run:
96 - `act.py`: is the script that runs the test
97 - -c acts_sanity_test_config: is the flag and name of the configuration file
99 - -tc IntegrationTest: is the name of the test case
[all …]
|
| /tools/tradefederation/core/proto/ |
| D | metric_measurement.proto | 11 * distributed under the License is distributed on an "AS IS" BASIS,
23 // Represents what is the expected directionality of the measurements
24 // For example: If we are measuring how fast a device is charging, the
35 // Represents whether the data was already processed or is raw data.
81 // Whether the measurements is raw data or processed.
|
| /tools/metalava/ |
| D | README.md | 7 Metalava is a metadata generator intended for the Android source tree, used for
20 * Diffing versions of the API and determining whether a newer version is
60 command line. If metalava is dropped into an Android framework build for
87 * Support for an updated signature file format (which is described in FORMAT.md)
101 files. This is vital now that some of these annotations become part of the
106 syntax. Since the goal is to have **all** API elements explicitly state
154 need to be able to figure out which parts of the source code is included in
155 the API and which one is implementation; it is simply handed the filtered API
160 is done for Java files.
175 StringBuilder.setLength(int) was missing from the API signatures since it is a
[all …]
|
| /tools/test/connectivity/acts/tests/google/wifi/rtt/ |
| D | README.md | 19 Where a test file is any of the `.py` files in any of the test sub-directories.
20 If a test class is specified, then all tests within that test class are executed.
40 The test configuration, the `<config>` in the commands above, is stored in
45 The only provided configuration is *wifi_rtt.json*.
56 of iterations or for the specified duration - whichever is longer.
58 RTT will run while a SoftAP (SAP) is enabled. The model name corresponds to the value returned by
|
| /tools/ndkports/ |
| D | README.md | 6 If you're an Android app developer looking to *consume* these libraries, this is
10 Note: Gradle support for consuming these artifacts from an AAR is a work in
15 Each third-party project is called a "port". Ports consist of a description of
19 A port is a subclass of the abstract Kotlin class `com.android.ndkports.Port`.
59 port is [ports/curl/port.kts](ports/curl/port.kts).
|
| /tools/tradefederation/core/tests/res/testCmdFiles/ |
| D | missing-begin-macro.txt | 11 # Note that "END MACRO" by itself is potentially a completely valid command.
12 # This will actually fail because the macro f() is now undefined.
|