| /frameworks/base/libs/androidfw/ |
| D | Android.bp | 128 "tests/CommonHelpers.cpp",
129 "tests/TestHelpers.cpp",
130 "tests/TestMain.cpp",
132 // Actual tests.
133 "tests/ApkAssets_test.cpp",
134 "tests/AppAsLib_test.cpp",
135 "tests/Asset_test.cpp",
136 "tests/AssetManager2_test.cpp",
137 "tests/AttributeFinder_test.cpp",
138 "tests/AttributeResolution_test.cpp",
[all …]
|
| /frameworks/base/libs/hwui/ |
| D | Android.bp | 270 test_suites: ["device-tests"],
272 "tests/common/scenes/*.cpp",
273 "tests/common/LeakChecker.cpp",
274 "tests/common/TestListViewSceneBase.cpp",
275 "tests/common/TestContext.cpp",
276 "tests/common/TestScene.cpp",
277 "tests/common/TestUtils.cpp",
282 // unit tests
302 "tests/unit/main.cpp",
303 "tests/unit/CacheManagerTests.cpp",
[all …]
|
| /frameworks/base/cmds/statsd/ |
| D | Android.bp | 243 test_suites: ["device-tests"],
263 "tests/AlarmMonitor_test.cpp",
264 "tests/anomaly/AlarmTracker_test.cpp",
265 "tests/anomaly/AnomalyTracker_test.cpp",
266 "tests/ConfigManager_test.cpp",
267 "tests/external/puller_util_test.cpp",
268 "tests/external/GpuStatsPuller_test.cpp",
269 "tests/external/IncidentReportArgs_test.cpp",
270 "tests/external/StatsPuller_test.cpp",
271 "tests/indexed_priority_queue_test.cpp",
[all …]
|
| /frameworks/compile/libbcc/tests/debuginfo/ |
| D | README | 4 This directory contains integration tests for debug information in libbcc.
6 The tests come in two flavours: host and target. Host tests are run on the
8 tests run on a live Android system (emulator or device.)
10 Host tests use clang to build bytecode (bc) files, which are then executed
16 Target tests are similar, but instead of using clang, they use ant and
19 The output is verified in the same way as host side tests, and the format
20 of the tests is the same.
22 *** If you are running target-side tests, you must disable parallel
28 To run the tests, you must have built the android source tree and have
52 To execute all the tests from this directory, use the llvm-lit tool:
[all …]
|
| /frameworks/base/cmds/idmap2/ |
| D | Android.bp | 96 test_suites: ["general-tests"],
98 "tests/BinaryStreamVisitorTests.cpp",
99 "tests/CommandLineOptionsTests.cpp",
100 "tests/FileUtilsTests.cpp",
101 "tests/Idmap2BinaryTests.cpp",
102 "tests/IdmapTests.cpp",
103 "tests/Main.cpp",
104 "tests/PoliciesTests.cpp",
105 "tests/PrettyPrintVisitorTests.cpp",
106 "tests/RawPrintVisitorTests.cpp",
[all …]
|
| /frameworks/compile/slang/tests/ |
| D | slang_test.py | 116 def ReportIfDifferFromExpected(tests, name, file1, file2): argument
128 tests.fail(err_message)
208 def CheckTestResult(dir_name, subprocess_ret, tests, args): argument
231 tests.fail(err_message)
242 tests.fail(err_message)
244 tests.fail('Invalid test name: ' + dir_name +
248 def CheckJavaOutput(tests): argument
264 tests.fail('%s not found' % find)
266 tests.fail('multiple %s found' % find)
268 tests.fail('%s and %s are different' % (found[0], expect))
[all …]
|
| /frameworks/base/core/tests/overlaytests/host/test-apps/UpdateOverlay/ |
| D | Android.mk | 18 LOCAL_MODULE_TAGS := tests
22 LOCAL_COMPATIBILITY_SUITE := general-tests
31 LOCAL_MODULE_TAGS := tests
34 LOCAL_COMPATIBILITY_SUITE := general-tests
43 LOCAL_MODULE_TAGS := tests
46 LOCAL_COMPATIBILITY_SUITE := general-tests
57 LOCAL_MODULE_TAGS := tests
60 LOCAL_COMPATIBILITY_SUITE := general-tests
68 LOCAL_MODULE_TAGS := tests
71 LOCAL_COMPATIBILITY_SUITE := general-tests
|
| /frameworks/compile/slang/lit-tests/ |
| D | README | 4 This directory contains tests for Slang that use the 'llvm-lit' testing tool.
10 To run the tests, you must have the android build environment variables
12 - Android version of llvm-lit (currently in libbcc/tests/debuginfo)
16 If you are unable to run the tests, try using the "--debug" option to llvm-lit.
19 the failure. Note that tests marked as "Expected Fail" (XFAIL) will not print
27 write tests that verify the emitted Java code.
31 To execute all the tests from this directory, use the Android llvm-lit tool
33 $ ../../libbcc/tests/debuginfo/llvm-lit .
39 Adding new tests
41 To add new tests, just add .rs files to a test directory with similar
[all …]
|
| /frameworks/native/services/surfaceflinger/CompositionEngine/ |
| D | Android.bp | 87 test_suites: ["device-tests"],
90 "tests/CompositionEngineTest.cpp",
91 "tests/DisplayColorProfileTest.cpp",
92 "tests/DisplayTest.cpp",
93 "tests/HwcBufferCacheTest.cpp",
94 "tests/LayerTest.cpp",
95 "tests/MockHWC2.cpp",
96 "tests/MockHWComposer.cpp",
97 "tests/OutputTest.cpp",
98 "tests/OutputLayerTest.cpp",
[all …]
|
| /frameworks/base/core/tests/overlaytests/host/test-apps/SignatureOverlay/ |
| D | Android.mk | 20 LOCAL_MODULE_TAGS := tests
23 LOCAL_COMPATIBILITY_SUITE := general-tests
28 LOCAL_MODULE_TAGS := tests
31 LOCAL_COMPATIBILITY_SUITE := general-tests
37 LOCAL_MODULE_TAGS := tests
40 LOCAL_COMPATIBILITY_SUITE := general-tests
|
| /frameworks/av/media/libaudioclient/tests/ |
| D | track_test_input_v1.0_ref.txt | 5 # sample rate tests
13 # format tests
17 # channel mask tests
21 # framecount tests
25 # shared memory tests
32 # session tests
34 # attributes tests
|
| D | record_test_input_v1.0_ref.txt | 5 # sample rate tests
13 # format tests
17 # channel mask tests
19 # frame count tests
26 # session tests
28 # input source tests
|
| /frameworks/base/packages/Tethering/tests/unit/ |
| D | Android.bp | 17 // Tests in this folder are included both in unit tests and CTS.
26 "net-tests-utils",
34 visibility: ["//cts/tests/tests/tethering"],
49 "net-tests-utils",
72 // Library containing the unit tests. This is used by the coverage test target to pull in the
73 // unit test code. It is not currently used by the tests themselves because all the build
74 // configuration needed by the tests is in the TetheringTestsDefaults rule.
79 "//frameworks/base/packages/Tethering/tests/integration",
87 "device-tests",
|
| /frameworks/opt/telephony/tests/telephonytests/ |
| D | Android.bp | 19 "net-tests-utils",
29 jarjar_rules: ":jarjar-rules-telephony-tests",
33 "device-tests",
38 name: "jarjar-rules-telephony-tests",
41 "jarjar-rules-tests.txt",
44 out: ["jarjar-rules-telephony-tests-combined.txt"],
|
| /frameworks/ml/nn/tools/test_generator/tests/ |
| D | test.py | 117 def ReportIfDifferFromExpected(tests, name, file1, file2): argument
129 tests.fail(err_message)
176 def CheckTestResult(dir_name, subprocess_ret, tests, args): argument
199 tests.fail(err_message)
210 tests.fail(err_message)
212 tests.fail('Invalid test name: ' + dir_name +
217 def ExecTest(dir_name, tests): argument
237 tests.fail('subprocess.call failed: ' + ' '.join(args))
242 CheckTestResult(dir_name, ret, tests, args)
244 ReportIfDifferFromExpected(tests, 'stdout', 'stdout.txt.expect', 'stdout.txt')
[all …]
|
| /frameworks/base/tests/ActivityManagerPerfTests/ |
| D | README.txt | 3 Performance tests for various ActivityManager components, e.g. Services, Broadcasts
4 * These are only for tests that don't require a target package to test against
5 * Self-contained perf tests should go in frameworks/base/apct-tests/perftests
7 Command to run tests
21 * tests
22 * Instrumentation test which runs the various performance tests and reports the results
29 Adding tests
31 * Look at tests/src/com/android/frameworks/perftests/am/BroadcastPerfTest and
37 * Add the test class under tests/src/com/android/frameworks/perftests/am/tests/
54 * Look at internal documentation for how to add new tests to dashboards and receive notification
|
| /frameworks/base/tests/SmokeTest/ |
| D | README | 1 The tests in this folder are a very controlled set of tests that will be run by
3 Please use caution when adding tests here.
5 If you wish to run these tests, issue the command:
8 -w com.android.smoketest/.tests.SmokeTestInstrumentationTestRunner
|
| /frameworks/opt/net/wifi/tests/wifitests/ |
| D | README.md | 2 This package contains unit tests for the android wifi service based on the
8 The easiest way to run tests is simply run
11 frameworks/opt/net/wifi/tests/wifitests/runtests.sh
15 connected device. It will then run the tests on the device.
17 See below for a few example of options to limit which tests are run.
27 If you manually build and push the test APK to the device you can run tests using
38 If you are trying to debug why tests are not doing what you expected, you can add android log
39 statements and use logcat to view them. The beginning and end of every tests is automatically logged
44 in this directory. It will rebuild parts of your tree with coverage enabled and then run the tests,
51 frameworks/opt/net/wifi/tests/wifitests/coverage.sh wifi_coverage
|
| /frameworks/base/test-runner/tests/src/android/test/suitebuilder/ |
| D | ListTestCaseNames.java | 30 List<Test> tests = Collections.<Test>list(suite.tests()); in getTestCaseNames() local
32 for (Test test : tests) { in getTestCaseNames()
46 List<Test> tests = Collections.<Test>list(suite.tests()); in getTestNames() local
48 for (Test test : tests) { in getTestNames()
|
| /frameworks/native/cmds/installd/tests/ |
| D | Android.bp | 1 // Build the unit tests for installd
4 test_suites: ["device-tests"],
23 test_suites: ["device-tests"],
48 test_suites: ["device-tests"],
73 test_suites: ["device-tests"],
100 test_suites: ["device-tests"],
|
| /frameworks/base/tests/DynamicCodeLoggerIntegrationTests/ |
| D | Android.mk | 23 LOCAL_MODULE_TAGS := tests
36 LOCAL_MODULE_TAGS := tests
49 LOCAL_MODULE_TAGS := tests
61 LOCAL_MODULE_TAGS := tests
64 LOCAL_COMPATIBILITY_SUITE := device-tests
|
| /frameworks/base/packages/Tethering/tests/integration/ |
| D | Android.bp | 27 "net-tests-utils",
47 visibility: ["//cts/tests/tests/tethering"]
55 "device-tests",
61 // Special version of the tethering tests that includes all tests necessary for code coverage
67 test_suites: ["device-tests", "mts"],
|
| /frameworks/base/lowpan/tests/ |
| D | README.md | 2 This package contains unit tests for the android LoWPAN framework System APIs based on the
8 The easiest way to run tests is simply run
11 frameworks/base/lowpan/tests/runtests.sh
15 connected device. It will then run the tests on the device.
27 See below for a few example of options to limit which tests are run.
37 If you manually build and push the test APK to the device you can run tests using
48 If you are trying to debug why tests are not doing what you expected, you can add android log
49 statements and use logcat to view them. The beginning and end of every tests is automatically logged
|
| /frameworks/base/wifi/tests/ |
| D | README.md | 2 This package contains unit tests for the android wifi framework APIs based on the
8 The easiest way to run tests is simply run
11 frameworks/base/wifi/tests/runtests.sh
15 connected device. It will then run the tests on the device.
27 See below for a few example of options to limit which tests are run.
37 If you manually build and push the test APK to the device you can run tests using
48 If you are trying to debug why tests are not doing what you expected, you can add android log
49 statements and use logcat to view them. The beginning and end of every tests is automatically logged
|
| /frameworks/rs/script_api/ |
| D | generate.sh | 50 rm -f ../../../cts/tests/tests/renderscript/src/android/renderscript/cts/generated/*
51 mv test/* ../../../cts/tests/tests/renderscript/src/android/renderscript/cts/generated/
62 mv slangtest/all$i.rscript ../../compile/slang/tests/P_all_api_$i
|