Home
last modified time | relevance | path

Searched refs:tests (Results 1 – 25 of 602) sorted by relevance

12345678910>>...25

/frameworks/base/libs/androidfw/
DAndroid.bp128 "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/cmds/statsd/
DAndroid.bp203 test_suites: ["device-tests"],
219 "tests/AlarmMonitor_test.cpp",
220 "tests/anomaly/AlarmTracker_test.cpp",
221 "tests/anomaly/AnomalyTracker_test.cpp",
222 "tests/ConfigManager_test.cpp",
223 "tests/external/puller_util_test.cpp",
224 "tests/external/GpuStatsPuller_test.cpp",
225 "tests/external/IncidentReportArgs_test.cpp",
226 "tests/external/StatsPuller_test.cpp",
227 "tests/indexed_priority_queue_test.cpp",
[all …]
/frameworks/base/libs/hwui/
DAndroid.bp276 test_suites: ["device-tests"],
278 "tests/common/scenes/*.cpp",
279 "tests/common/LeakChecker.cpp",
280 "tests/common/TestListViewSceneBase.cpp",
281 "tests/common/TestContext.cpp",
282 "tests/common/TestScene.cpp",
283 "tests/common/TestUtils.cpp",
288 // unit tests
308 "tests/unit/main.cpp",
309 "tests/unit/CacheManagerTests.cpp",
[all …]
/frameworks/compile/libbcc/tests/debuginfo/
DREADME4 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/opt/gamesdk/third_party/protobuf-3.0.0/jenkins/
Dmake_test_output.py26 tests = defaultdict(dict)
38 test = tests[name]
50 test = tests[testname]
60 tests["cpp"]["name"] = "cpp"
63 tests["cpp"]["time"] = f.read().strip()
64 tests["cpp"]["failure"] = False
66 ret = tests.values()
71 def genxml(tests): argument
76 for test in tests:
/frameworks/base/cmds/idmap2/
DAndroid.bp87 test_suites: ["general-tests"],
89 "tests/BinaryStreamVisitorTests.cpp",
90 "tests/CommandLineOptionsTests.cpp",
91 "tests/FileUtilsTests.cpp",
92 "tests/Idmap2BinaryTests.cpp",
93 "tests/IdmapTests.cpp",
94 "tests/Main.cpp",
95 "tests/PoliciesTests.cpp",
96 "tests/PrettyPrintVisitorTests.cpp",
97 "tests/RawPrintVisitorTests.cpp",
[all …]
/frameworks/compile/slang/tests/
Dslang_test.py116 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/
DAndroid.mk18 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/native/services/surfaceflinger/CompositionEngine/
DAndroid.bp87 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/compile/slang/lit-tests/
DREADME4 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/base/core/tests/overlaytests/host/test-apps/SignatureOverlay/
DAndroid.mk20 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/
Dtrack_test_input_v1.0_ref.txt5 # sample rate tests
13 # format tests
17 # channel mask tests
21 # framecount tests
25 # shared memory tests
32 # session tests
34 # attributes tests
Drecord_test_input_v1.0_ref.txt5 # sample rate tests
13 # format tests
17 # channel mask tests
19 # frame count tests
26 # session tests
28 # input source tests
/frameworks/ml/nn/tools/test_generator/tests/
Dtest.py117 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/SmokeTest/
DREADME1 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/base/tests/ActivityManagerPerfTests/
DREADME.txt3 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/opt/gamesdk/third_party/protobuf-3.0.0/ruby/
DRakefile81 # Proto for tests.
82 genproto_output << "tests/generated_code.rb"
83 genproto_output << "tests/test_import.rb"
84 file "tests/generated_code.rb" => "tests/generated_code.proto" do |file_task|
85 sh "../src/protoc --ruby_out=. tests/generated_code.proto"
88 file "tests/test_import.rb" => "tests/test_import.proto" do |file_task|
89 sh "../src/protoc --ruby_out=. tests/test_import.proto"
102 t.test_files = FileList["tests/*.rb"]
/frameworks/opt/net/wifi/tests/wifitests/
DREADME.md2 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/tests/DynamicCodeLoggerIntegrationTests/
DAndroid.mk23 LOCAL_MODULE_TAGS := tests
36 LOCAL_MODULE_TAGS := tests
50 LOCAL_MODULE_TAGS := tests
62 LOCAL_MODULE_TAGS := tests
65 LOCAL_COMPATIBILITY_SUITE := device-tests
/frameworks/base/test-runner/tests/src/android/test/suitebuilder/
DListTestCaseNames.java30 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/
DAndroid.bp1 // 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"],
98 test_suites: ["device-tests"],
/frameworks/opt/gamesdk/third_party/protobuf-3.0.0/conformance/
DREADME.md8 This directory contains conformance tests for testing completeness and
9 correctness of Protocol Buffers implementations. These tests are designed
13 contains all of the tests themselves. Then separate programs written
17 Before running any of these tests, make sure you run `make` in the base
18 directory to build `protoc`, since all the tests depend on it.
22 Then to run the tests against the C++ implementation, run:
26 More tests and languages will be added soon!
31 To run these tests against a new Protocol Buffers implementation, write a
/frameworks/base/lowpan/tests/
DREADME.md2 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/
DREADME.md2 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/
Dgenerate.sh50 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.rs ../../compile/slang/tests/P_all_api_$i

12345678910>>...25