Home
last modified time | relevance | path

Searched refs:to (Results 1 – 25 of 93) sorted by relevance

1234

/tools/test/connectivity/acts/tests/google/bt/pts/instructions/
DHOGP_PTS_INSTRUCTIONS9 # Unless required by applicable law or agreed to in writing, software
22 [PTS Interaction] Enter PIN from phone to PTS
30 [PTS Interaction] Enter PIN from phone to PTS
38 [PTS Interaction] Enter PIN from phone to PTS
46 [PTS Interaction] Enter PIN from phone to PTS
55 [PTS Interaction] Enter PIN from phone to PTS
64 [PTS Interaction] Enter PIN from phone to PTS
77 [PTS Interaction] Enter PIN from phone to PTS
86 [PTS Interaction] Enter PIN from phone to PTS
99 [PTS Interaction] Enter PIN from phone to PTS
[all …]
DL2CAP_PTS_INSTRUCTIONS9 # Unless required by applicable law or agreed to in writing, software
21 [Wait up to 10-15 seconds]
27 [Wait up to 10-15 seconds]
33 [Wait up to 10-15 seconds]
37 [Wait up to 10-15 seconds]
41 [Wait up to 10-15 seconds]
50 [Wait up to 10-15 seconds]
64 [Wait up to 10-15 seconds]
69 [Wait up to 10-15 seconds]
75 [Wait up to 10-15 seconds]
[all …]
DGAP_PTS_INSTRUCTIONS9 # Unless required by applicable law or agreed to in writing, software
17 Note: Use this stack change to test all LE testcases:
18 …rce.com/#/c/319838/1/stack/btm/btm_ble_multi_adv.cc TSPC_bd_addr_iut should be set to 4AF441CF285A.
19 This sets the random address to a static address.
48 [PTS Interaction] Answer NO to non-connectable adv question
138 Note: PTS is very flacky, rerun multiple times to pass.
189 Note: Run the test a first time and it will fail. Change the address to
194 Set PTS IXIT value iut_privacy_enabled to False
199 Enter pin from phone to PTS
200 [PTS Interactoin] OK to disconnect
[all …]
DSM_PTS_INSTRUCTIONS9 # Unless required by applicable law or agreed to in writing, software
48 [Enter Pin from console to PTS]
59 [Enter Pin from console to PTS]
66 [Enter Pin from console to PTS]
73 [Enter Pin from console to PTS]
91 [Enter Pin from console to PTS]
98 [Enter Pin from console to PTS]
105 [Enter Pin from console to PTS]
112 [Enter Pin from console to PTS]
115 Need to be able to send security request via cmd line
[all …]
/tools/tradefederation/core/atest/docs/
Ddeveloper_workflow.md3 This document explains the practical steps for contributing code to atest.
16 this division, your first step should be to identify the code
19 referring to it as the "Python Code".
24 Its job is to translate user inputs into (1) build targets and (2)
25 information needed for the test runner to run the test. It then invokes
26 the appropriate test runner code to run the tests. As the tests
28 the user. It uses Test Finder and Test Runner classes to do this work.
30 code you'll want to work on.
41 involves how the test is actually run, you'll need to work with this
56 (path relative to android repo root)
[all …]
Datest_structure.md3 You're here because you'd like to contribute to atest. To start off, we'll
5 do. If you're more interested in how to use atest, go to the [README](../README.md).
28 module-info.json file (and build it if it's not detected or we want to rebuild
32 process. We create the results dir for our test runners to dump results in and
33 proceed to the first juicy part of atest, finding tests.
35 The tests specified by the user are passed into the ```CLITranslator``` to
37 required and optional bits used to run the test as how the user intended.
39 used to run the test. Optional bits would be additional args for the test and
46 The final step is to run the tests which is where the test runners do their job.
49 the ```AtestTradefedTestRunner``` is used to kick off ```hello_world_test```.
[all …]
Ddevelop_test_runners.md3 Learn about test runners and how to create a new test runner class.
14 top-level args consumed by atest passed onto the test runner. It is up to the
15 test runner to translate those args into the specific args the test runner
18 can have a consistent CLI for args instead of requiring the users to remember
20 determine its specific dependencies that need to be built prior to any test
25 First thing to choose is where to put the test runner. This will primarily
33 > rules apply, rerun ```build/envsetup.sh``` to update ```$PYTHONPATH```.
37 to see what a simple test runner will look like.
40 You'll need to override the following parent methods:
44 to be built prior to test execution.
[all …]
Ddevelop_test_finders.md3 Learn about test finders and how to create a new test finder class.
12 user input) and should try to resolve that string into a ```TestInfo``` object.
14 a data field to hold misc bits like filters and extra args for the test. 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
24 file name patterns, a special file in a dir to indicate it's a test, etc. The
30 First thing to choose is where to put the test finder. This will primarily
38 > rules apply, rerun ```build/envsetup.sh``` to update ```$PYTHONPATH```.
42 create a list of find methods that ```test_finder_handler``` will use to collect
48 field as a dict. Check out ```ExampleFinder``` to see how the data field is
[all …]
/tools/tradefederation/core/src/com/android/tradefed/util/
DDirectedGraph.java67 public void addEdge(V from, V to) { in addEdge() argument
69 this.addVertice(to); in addEdge()
70 neighbors.get(from).add(to); in addEdge()
78 public void removeEdge(V from, V to) { in removeEdge() argument
79 if (!(this.contains(from) && this.contains(to))) { in removeEdge()
82 neighbors.get(from).remove(to); in removeEdge()
96 for (V to: neighbors.get(from)) { in inDegree()
97 result.put(to, result.get(to) + 1); in inDegree()
/tools/external/fat32lib/
DNOTICE7 Everyone is permitted to copy and distribute verbatim copies
15 …to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are…
17 …to some specially designated software packages--typically libraries--of the Free Software Foundati…
19 …e, we are referring to freedom of use, not price. Our General Public Licenses are designed to make…
21 …need to make restrictions that forbid distributors to deny you these rights or to ask you to surre…
23 …t provide complete object files to the recipients, so that they can relink them with the library a…
25 …brary, and (2) we offer you this license, which gives you legal permission to copy, distribute and…
27 To protect each distributor, we want to make it very clear that there is no warranty for the free l…
29 Finally, software patents pose a constant threat to the existence of any free program. We wish to m…
31 … to certain designated libraries, and is quite different from the ordinary General Public License.…
[all …]
/tools/repohooks/
DREADME.md9 turn on any hook it wishes to enforce.
13 Normally these execute automatically when you run `repo upload`. If you want to
20 Sometimes you might want to bypass the upload checks. While this is **strongly
23 `--no-verify` when running `repo upload` to skip all upload checks. This will
42 Simply check this in to the manifest git repo and you're done.
53 in subdirectories (to try and override parent settings) is not supported.
77 generally be relative to that point.
79 A few environment variables are set so scripts don't need to discover things.
83 * `REPO_PATH`: The path to the project relative to the root.
87 * `REPO_LREV`: The name of the remote revision, translated to a local tracking
[all …]
/tools/tradefederation/core/tests/res/config/suite/
Dsuite.md3 A suite allows one to run a group of tests for a given build. Adding or removing
7 change to pull it out of presubmit check.
9 A test can also be easily added to multiple suites by specifying the suite name
10 in the test config file. So one doesn't need to maintain a collection of test in
11 complicated GCL files, for a test to run in multiple suites.
17 Suite configuration file is similar to a TradeFed test configuration file. It
20 file has option "test-suite-tag" set to that value will be included in that
34 1. Add test to suite
36 To include a test in the suite, it must be built to device-tests or
43 The test configuration file should also have option "test-suite-tag" set to the
[all …]
/tools/test/connectivity/acts/tests/google/tel/config/
DREADME.md2 …ifferences from other ACTS configs that require additional keys to be defined in order to run near…
5 …- **no_bug_report_on_fail** - The default behavior of telephony tests is to capture a bug report a…
6 …to a SIM card config file, which is needed in the event that the MSISDN/MDN is not programmed onto…
8 …ucture sometimes yields flaky results, when no other options are available to mitigate this uncert…
9 - **wifi_network_pass** - The password to the network specified by *wifi_network_ssid*.
12 … power in mW that can be used in steady state during calling power tests in order to pass the test.
13 … of power in mW that can be used in steady state during idle power tests in order to pass the test.
15 - **phone_call_iteration** - The number of calls to be placed in TelLiveStressCallTest
/tools/apkzlib/src/test/resources/testData/packaging/text-files/
Drfc2460.txt21 improvements. Please refer to the current edition of the "Internet
32 also sometimes referred to as IP Next Generation or IPng.
54 8.4 Responding to Packets Carrying Routing Headers..........29
75 designed as the successor to IP version 4 (IPv4) [RFC-791]. The
76 changes from IPv4 to IPv6 fall primarily into the following
81 IPv6 increases the IP address size from 32 bits to 128 bits, to
85 adding a "scope" field to multicast addresses. And a new type
86 of address called an "anycast address" is defined, used to send
87 a packet to any one of a group of nodes.
91 Some IPv4 header fields have been dropped or made optional, to
[all …]
/tools/tradefederation/core/tests/test-apps/NativeTestSampleApp/tests/
DAndroid.mk.bak9 # Unless required by applicable law or agreed to in writing, software
15 # Makefile to build device-based native tests for a test static library.
18 # long-term need to build this against prebuilt NDK
31 # Library to be tested
39 # The standard naming should conform to: <module_being_tested>tests
43 # to $(TARGET_OUT_DATA_NATIVE_TESTS)/$(LOCAL_MODULE) - only define this if you
44 # want to override the default location to use a different subdirectory, such as:
/tools/apksig/
DLICENSE7 Unless required by applicable law or agreed to in writing, software
31 "control" means (i) the power, direct or indirect, to cause the
40 including but not limited to software source code, documentation
45 not limited to compiled object code, generated documentation,
46 and conversions to other media types.
50 copyright notice that is included in or attached to the work
58 separable from, or merely link (or bind by name) to the interfaces of,
63 to that Work or Derivative Works thereof, that is intentionally
64 submitted to Licensor for inclusion in the Work by the copyright owner
65 or by an individual or Legal Entity authorized to submit on behalf of
[all …]
DREADME.md3 apksig is a project which aims to simplify APK signing and checking whether APK signatures are
4 expected to verify on Android. apksig supports
8 Android Nougat, API Level 24). apksig is meant to be used outside of Android devices.
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
32 which need to perform signing while building an APK, instead of after. For simpler use cases
33 where the APK to be signed is available upfront, the `ApkSigner` above is easier to use.
37 classes may change any time without regard to existing clients outside of `apksig` and `apksigner`._
46 * check whether the provided APK's signatures are expected to verify on all Android platforms
/tools/acloud/
DLICENSE19 "control" means (i) the power, direct or indirect, to cause the
28 including but not limited to software source code, documentation
33 not limited to compiled object code, generated documentation,
34 and conversions to other media types.
38 copyright notice that is included in or attached to the work
46 separable from, or merely link (or bind by name) to the interfaces of,
51 to that Work or Derivative Works thereof, that is intentionally
52 submitted to Licensor for inclusion in the Work by the copyright owner
53 or by an individual or Legal Entity authorized to submit on behalf of
56 to the Licensor or its representatives, including but not limited to
[all …]
/tools/tradefederation/core/atest/
DREADME.md3 Atest is a command line tool that allows users to build, install and run Android tests locally.
4 This markdown will explain how to use atest on the commandline to run android tests.<br>
7 Importantly, when writing your test's build script file (Android.mk), make sure to include
8 the variable `LOCAL_COMPATIBILITY_SUITE`. A good default to use for it is `device-test`.
10 Curious about how atest works? Want to add a feature but not sure where to begin? [Go here.](./docs…
11 Just want to learn about the overall structure? [Go here.](./docs/atest_structure.md)
25 Before you can run atest, you first have to setup your environment.
34 Run the `$ lunch` command to bring up a "menu" of supported devices. Find the device that matches
42 atest command to your $PATH.
48 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;**atest \<optional arguments> \<tests to run>**
[all …]
/tools/acloud/internal/proto/
Dinternal_config.proto9 // Unless required by applicable law or agreed to in writing, software
19 // Default values to use when user did not provide a value.
56 // If file is of this type, it will be compressed to avd-system.tar.gz
58 // Default data disk device to use when extra_data_disk_size_gb
61 // A map from size_gb to the name of a precreated_data_image
74 // It is used during the Oauth2 authentication flow. It is okay to
77 // Error messages to be displayed to user when the user
78 // does not have access to the cloud project.
80 // Value is the error message to show.
/tools/apksig/src/apksigner/java/com/android/apksigner/
Dhelp_sign.txt6 signer. For each signer, you need to provide the signer's private key and
12 --in Input APK file to sign. This is an alternative to
17 --out File into which to output the signed APK. By default, the
22 --v1-signing-enabled Whether to enable signing using JAR signing scheme (aka v1
27 --v2-signing-enabled Whether to enable signing using APK Signature Scheme v2
41 --debuggable-apk-permitted Whether to permit signing android:debuggable="true"
46 app. It is a good security practice to not sign
60 need to use this option when only one signer is used.
67 There are two ways to provide the signer's private key and certificate: (1) Java
89 A password is required to open a KeyStore.
[all …]
Dhelp_verify.txt6 --min-sdk-version and/or --max-sdk-version to verify the APK against a custom
25 --in APK file to verify. This is an alternative to specifying
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
/tools/tradefederation/core/atest/unittest_data/vts_push_files/
Dpush_file2.push1 push_file2_target1->/path/to/push_file2_target1
2 push_file2_target2->/path/to/push_file2_target2
/tools/test/connectivity/acts/tests/google/wifi/aware/
DREADME.md3 This directory contains ACTS/sl4a test scripts to verify and characterize
13 fail criteria - that criteria may not apply to all implementations.
14 * stress: Tests which run through a large number of iterations to stress
17 not provided or may not apply to all implementations or test environments.
19 in a particular mode and expect the tester to capture an over-the-air
33 directory which lists all tests in the directory. E.g. to execute all functional
43 define the following key to configure the test:
45 * **aware_default_power_mode**: The power mode in which to run all tests. Options
/tools/metalava/
DREADME.md11 and more importantly to hide code intended to be implementation only, driven
39 metalava extracts metadata from source code to generate artifacts such as the
74 * Ability to read in an existing android.jar file instead of from source, which means
75 we can regenerate signature files etc for older versions according to new formats
76 (e.g. to fix past errors in doclava, such as annotation instance methods which were
79 * Ability to merge in data (annotations etc) from external sources, such as
103 the goal is to have **all** API elements explicitly state their nullness
135 * Misc documentation handling; for example, it attempts to fix sentences
152 code). This means that the documentation tool itself does not need to be able to
163 nullness, such as attempting to change a nullness contract incompatibly
[all …]

1234