| /tools/asuite/atest-py2/ |
| D | result_reporter.py | 88 def update_perf_info(self, test): argument
94 all_additional_keys = set(test.additional_info.keys())
99 benchmark_info['test_name'] = test.test_name
100 for key, data in test.additional_info.items():
274 def process_test_result(self, test): argument
280 if test.runner_name not in self.runners:
281 self.runners[test.runner_name] = OrderedDict()
282 assert self.runners[test.runner_name] != FAILURE_FLAG
283 self.all_test_results.append(test)
284 if test.group_name not in self.runners[test.runner_name]:
[all …]
|
| D | cli_translator.py | 81 def _find_test_infos(self, test, tm_test_detail): argument
99 self.mod_info, test):
105 finder.test_finder_instance, test)
121 atest_utils.colorize(test, constants.GREEN),
129 f_results = self._fuzzy_search_and_msg(test, find_test_err_msg)
138 test_reference=test,
145 atest_utils.update_test_info_cache(test, test_infos)
149 def _fuzzy_search_and_msg(self, test, find_test_err_msg): argument
160 atest_utils.colorize(test, constants.RED))
164 results = mod_finder.get_fuzzy_searching_results(test)
[all …]
|
| /tools/metalava/src/test/java/com/android/tools/metalava/ |
| D | ShowForStubPurposesAnnotationTest.kt | 225 fun `Hierarchy test - SystemApi + ModuleApi`() { in Hierarchy test - SystemApi + ModuleApi()
281 fun `Hierarchy test - SystemApi only`() { in Hierarchy test - SystemApi only()
317 fun `Hierarchy test - ModuleApi Only, also check the stub files`() { in Hierarchy test - ModuleApi Only, also check the stub files()
437 fun `Hierarchy test - Can't refer from system to module`() { in Hierarchy test - Can't refer from system to module()
503 package test.pkg;
506 @test.annotation.Hide
507 @test.annotation.SystemApi
510 @test.annotation.Hide
511 @test.annotation.SystemApi
514 @test.annotation.Hide
[all …]
|
| /tools/asuite/atest/ |
| D | result_reporter.py | 101 def update_perf_info(self, test): argument
107 all_additional_keys = set(test.additional_info.keys())
112 benchmark_info['test_name'] = test.test_name
113 for key, data in test.additional_info.items():
291 def process_test_result(self, test): argument
297 if test.runner_name not in self.runners:
298 self.runners[test.runner_name] = OrderedDict()
299 assert self.runners[test.runner_name] != FAILURE_FLAG
300 self.all_test_results.append(test)
301 if test.group_name not in self.runners[test.runner_name]:
[all …]
|
| D | cli_translator.py | 98 def _find_test_infos(self, test, tm_test_detail): argument
115 test_name, mainline_modules = atest_utils.parse_mainline_modules(test)
119 self.mod_info, test)
153 test_info.test_name = test
168 atest_utils.colorize(test, constants.GREEN),
176 f_results = self._fuzzy_search_and_msg(test, find_test_err_msg)
185 test_reference=test,
192 atest_utils.update_test_info_cache(test, test_infos)
197 def _verified_mainline_modules(self, test, mainline_modules): argument
215 if not self.mod_info.is_module(test):
[all …]
|
| /tools/asuite/atest/docs/ |
| D | atest_structure.md | 10 3. [Test Finders](#test-finders)
11 4. [Test Runners](#test-runners)
16 Atest is primarily composed of 2 components: [test finders](#test-finders) and
17 [test runners](#test-runners). At a high level, atest does the following:
19 2. Find test(s) based on user input
20 3. Build test dependencies
21 4. Run test(s)
31 compatibility_suite, auto_gen_config, etc) that is used during the test finding
32 process. We create the results dir for our test runners to dump results in and
37 required and optional bits used to run the test as how the user intended.
[all …]
|
| D | develop_test_runners.md | 3 Learn about test runners and how to create a new test runner class.
6 1. [Test Runner Details](#test-runner-details)
7 2. [Creating a Test Runner](#creating-a-test-runner)
9 ## <a name="test-runner-details">Test Runner Details</a>
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
15 test runner to translate those args into the specific args the test runner
16 accepts. In this way, you can think of the test runner as a translator between
17 the atest CLI and your test runner's CLI. The reason for this is so that atest
19 the differing CLIs of various test runners. The test runner should also
[all …]
|
| D | develop_test_finders.md | 3 Learn about test finders and how to create a new test finder class.
6 1. [Test Finder Details](#test-finder-details)
7 2. [Creating a Test Finder](#creating-a-test-finder)
9 ## <a name="test-finder-details">Test Finder Details</a>
11 A test finder class holds find methods. A find method is given a string (the
13 A ```TestInfo``` object holds the test name, test dependencies, test runner, and
14 a data field to hold misc bits like filters and extra args for the test. The
15 test finder class can hold multiple find methods. The find methods are grouped
16 together in a class so they can share metadata for optimal test finding.
18 the test configs for the ```TFIntegrationFinder```.
[all …]
|
| /tools/asuite/atest-py2/docs/ |
| D | atest_structure.md | 10 3. [Test Finders](#test-finders)
11 4. [Test Runners](#test-runners)
16 Atest is primarily composed of 2 components: [test finders](#test-finders) and
17 [test runners](#test-runners). At a high level, atest does the following:
19 2. Find test(s) based on user input
20 3. Build test dependencies
21 4. Run test(s)
31 compatibility_suite, auto_gen_config, etc) that is used during the test finding
32 process. We create the results dir for our test runners to dump results in and
37 required and optional bits used to run the test as how the user intended.
[all …]
|
| D | develop_test_runners.md | 3 Learn about test runners and how to create a new test runner class.
6 1. [Test Runner Details](#test-runner-details)
7 2. [Creating a Test Runner](#creating-a-test-runner)
9 ## <a name="test-runner-details">Test Runner Details</a>
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
15 test runner to translate those args into the specific args the test runner
16 accepts. In this way, you can think of the test runner as a translator between
17 the atest CLI and your test runner's CLI. The reason for this is so that atest
19 the differing CLIs of various test runners. The test runner should also
[all …]
|
| D | develop_test_finders.md | 3 Learn about test finders and how to create a new test finder class.
6 1. [Test Finder Details](#test-finder-details)
7 2. [Creating a Test Finder](#creating-a-test-finder)
9 ## <a name="test-finder-details">Test Finder Details</a>
11 A test finder class holds find methods. A find method is given a string (the
13 A ```TestInfo``` object holds the test name, test dependencies, test runner, and
14 a data field to hold misc bits like filters and extra args for the test. The
15 test finder class can hold multiple find methods. The find methods are grouped
16 together in a class so they can share metadata for optimal test finding.
18 the test configs for the ```TFIntegrationFinder```.
[all …]
|
| /tools/asuite/atest/test_finders/ |
| D | module_finder.py | 110 def _update_to_vts_test_info(self, test): argument
122 test.test_runner = self._VTS_TEST_RUNNER
124 test.data[constants.TI_REL_CONFIG])
143 test.build_targets |= test_finder_utils.get_targets_from_vts_xml(
145 test.build_targets.add('vts-test-core')
146 test.build_targets.add(test.test_name)
147 return test
149 def _update_legacy_robolectric_test_info(self, test): argument
165 test.test_runner = self._ROBOLECTRIC_RUNNER
166 test.test_name = self.module_info.get_robolectric_test_name(test.test_name)
[all …]
|
| /tools/test/connectivity/acts_tests/tests/google/wifi/rtt/ |
| D | README.md | 3 This directory contains ACTS/sl4a test scripts to verify and characterize
11 test the implementation. Considering that some failures are expected,
13 not provided or may not apply to all implementations or test environments.
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.
23 The Wi-Fi RTT tests support several different test scenarios which require different test bed
24 configuration. The test beds and their corresponding test files are:
40 The test configuration, the `<config>` in the commands above, is stored in
47 The configuration defines the following keys to configure the test:
51 configuration of the AP used in the test.
[all …]
|
| /tools/security/sanitizer-status/ |
| D | sanitizer-status.cpp | 134 int test(void (*function)()) { in test() function
187 asan_failures += test(test_crash_malloc_overflow); in main()
188 asan_failures += test(test_crash_malloc_uaf); in main()
189 asan_failures += test(test_crash_stack); in main()
206 hwasan_failures += test(test_crash_malloc_overflow); in main()
207 hwasan_failures += test(test_crash_malloc_uaf); in main()
208 hwasan_failures += test(test_crash_stack); in main()
209 hwasan_failures += test(test_crash_pthread_mutex_unlock); in main()
220 msan_failures += test(test_msan_crash_stack); in main()
253 ubsan_failures += test(test_integer_overflow); in main()
[all …]
|
| /tools/asuite/atest/bazel/ |
| D | atest_bazel_mode.md | 3 without requiring knowledge of Trade Federation test harness command line
25 <p>Note: "--host" is needed to run the test completely on the host without a device.
27 To run multiple tests, separate test references with spaces. For example:
33 >```$ atest --bazel-mode --host --host-unit-test-only```
38 command increases the test timeout:
46 files to correctly invoke ```bazel test``` command. The Bazel BUILD files are
57 test = "//platform_testing/tests/example/jarhosttest:HelloWorldHostTest",
77 At last, ```bazel test``` command is executed for the test targets.
82 * In Atest Standard Mode, user can view detailed test case result in the
83 terminal, while in Bazel Mode only test target result is showing. For test case
[all …]
|
| /tools/test/connectivity/acts_tests/acts_contrib/test_utils_tests/power/tel/lab/ |
| D | power_tel_traffic_e2e_test.py | 58 test = self.PTTT(test_run_config)
61 test.unpack_userparams(
90 test.setup_class()
91 test.setup_test()
92 test.power_tel_traffic_test()
93 test.teardown_test()
94 test.teardown_class()
96 self.assertTrue(test.start_tel_traffic.called,
98 self.assertTrue(test.init_simulation.called,
100 self.assertTrue(test.initialize_simulator.called,
[all …]
|
| D | initialize_simulator_test.py | 42 test = self.PCBT(test_run_config)
43 self.test = test
49 self.test.unpack_userparams(md8475_version='A', md8475a_ip_address='12345')
54 result = self.test.initialize_simulator()
65 self.test.unpack_userparams(md8475_version='B', md8475a_ip_address='12345')
70 result = self.test.initialize_simulator()
81 self.test.unpack_userparams(md8475_version=None,
89 result = self.test.initialize_simulator()
100 self.test.unpack_userparams(md8475_version=None,
106 self.test.initialize_simulator()
|
| D | init_simulation_test.py | 42 test = self.PCBT(test_run_config)
43 self.test = test
50 self.test.unpack_userparams(simulation=mock_lte_sim)
52 self.test.init_simulation(self.PCBT.PARAM_SIM_TYPE_LTE)
55 self.assertTrue(self.test.simulation is mock_lte_sim,
62 self.test.unpack_userparams(simulation=mock.Mock(spec=LteSimulation),
68 self.test.init_simulation(self.PCBT.PARAM_SIM_TYPE_UMTS)
78 self.test.unpack_userparams(simulation=mock.Mock(spec=LteSimulation))
80 self.test.init_simulation('Invalid simulation type')
|
| /tools/asuite/atest-py2/test_finders/ |
| D | module_finder.py | 87 def _update_to_vts_test_info(self, test): argument
99 test.test_runner = self._VTS_TEST_RUNNER
101 test.data[constants.TI_REL_CONFIG])
120 test.build_targets |= test_finder_utils.get_targets_from_vts_xml(
122 test.build_targets.add('vts-test-core')
123 test.build_targets.add(test.test_name)
124 return test
126 def _update_to_robolectric_test_info(self, test): argument
135 test.test_runner = self._ROBOLECTRIC_RUNNER
136 test.test_name = self.module_info.get_robolectric_test_name(test.test_name)
[all …]
|
| /tools/test/connectivity/acts_tests/tests/google/wifi/aware/ |
| D | README.md | 3 This directory contains ACTS/sl4a test scripts to verify and characterize
15 test the implementation. Considering that some failures are expected,
17 not provided or may not apply to all implementations or test environments.
24 1. Individual test(s): `act.py -c <config> -tc {<test_class>|<test_class>:<test_name>}`
26 Where a test file is any of the `.py` files in any of the test sub-directories.
27 If a test class is specified, then all tests within that test class are executed.
29 2. All tests in a test group: `act.py -c <config> -tf <test_file>`
31 Where `<test_file>` is a file containing a list of tests. Each of the test
36 `act.py -c <config> -tf ./tools/test/connectivity/acts_tests/tests/google/wifi/aware/functional/fun…
39 The test configurations, the `<config>` in the commands above, are stored in
[all …]
|
| /tools/asuite/atest/bazel/reporter/src/com/android/tradefed/result/ |
| D | BazelXmlResultReporter.java | 124 public void testStarted(TestDescription test) { in testStarted() argument
125 testStarted(test, System.currentTimeMillis()); in testStarted()
129 public void testStarted(TestDescription test, long startTime) { in testStarted() argument
130 mTestRunResult.testStarted(test, startTime); in testStarted()
134 public void testEnded(TestDescription test, HashMap<String, Metric> testMetrics) { in testEnded() argument
135 testEnded(test, System.currentTimeMillis(), testMetrics); in testEnded()
139 public void testEnded(TestDescription test, long endTime, HashMap<String, Metric> testMetrics) { in testEnded() argument
140 mTestRunResult.testEnded(test, endTime, testMetrics); in testEnded()
144 public void testFailed(TestDescription test, String trace) { in testFailed() argument
145 mTestRunResult.testFailed(test, trace); in testFailed()
[all …]
|
| /tools/security/remote_provisioning/cert_validator/src/ |
| D | lib.rs | 21 #[cfg(test)]
27 #[test]
39 #[test]
58 #[test]
68 #[test]
77 #[test]
85 #[test]
93 #[test]
101 #[test]
107 #[test]
[all …]
|
| /tools/asuite/atest/unittest_data/ |
| D | VtsAndroidTest.xml.data | 14 <test class="com.android.tradefed.testtype.VtsMultiDeviceTest">
15 <option name="test-module-name" value="VtsTestName"/>
16 <option name="binary-test-working-directory" value="_32bit::/data/nativetest/" />
17 <option name="binary-test-working-directory" value="_64bit::/data/nativetest64/" />
18 …<option name="binary-test-source" value="_32bit::DATA/nativetest/vts_treble_vintf_test/vts_treble_…
19 …<option name="binary-test-source" value="_64bit::DATA/nativetest64/vts_treble_vintf_test/vts_trebl…
20 <option name="binary-test-source" value="target_with_delim->/path/to/target_with_delim" />
21 <option name="binary-test-source" value="out/dir/target" />
22 <option name="binary-test-type" value="gtest"/>
23 <option name="test-timeout" value="5m"/>
[all …]
|
| /tools/ndkports/googletest/ |
| D | build.gradle.kts | 56 findTests(buildDir.resolve("googlemock")).forEach { test -> in <lambda>() method
57 push(test, File("googlemock").resolve(test.name)) in <lambda>()
59 findTests(buildDir.resolve("googletest")).forEach { test -> in <lambda>() method
60 push(test, File("googletest").resolve(test.name)) in <lambda>()
66 findTests(buildDir.resolve("googlemock")).forEach { test -> in <lambda>() method
68 test.name, listOf( in <lambda>()
76 findTests(buildDir.resolve("googletest")).forEach { test -> in <lambda>() method
78 test.name, listOf( in <lambda>()
|
| /tools/test/connectivity/acts/ |
| D | README.md | 6 of utility functions to further ease test development. It is an ideal desktop
8 path, performing confidence testing, or running extended regression test suites.
21 it is recommended for all new test cases.
33 $ python3 setup.py test
34 $ python setup.py test
41 3. Sequentially execute test classes
96 - `act.py`: is the script that runs the test
98 to be used in the test
99 - -tc IntegrationTest: is the name of the test case
105 a list of paths where the python test case files are located. Below are the
[all …]
|