/frameworks/base/libs/hwui/ |
D | Android.bp | 273 test_suites: ["device-tests"], 275 "tests/common/scenes/*.cpp", 276 "tests/common/LeakChecker.cpp", 277 "tests/common/TestListViewSceneBase.cpp", 278 "tests/common/TestContext.cpp", 279 "tests/common/TestScene.cpp", 280 "tests/common/TestUtils.cpp", 285 // unit tests 303 "tests/unit/main.cpp", 304 "tests/unit/BakedOpDispatcherTests.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/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/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/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/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/base/packages/Osu2/tests/ |
D | README.md | 2 This package contains unit tests for the OSU app based on the 8 The easiest way to run tests is simply run 11 frameworks/base/packages/Osu2/tests/runtests.sh 15 connected device. It will then run the tests on the device. 22 See below for a few example of options to limit which tests are run. 32 If you manually build and push the test APK to the device you can run tests using 35 adb shell am instrument -w 'com.android.osu.tests/android.support.test.runner.AndroidJUnitRunner' 43 If you are trying to debug why tests are not doing what you expected, you can add android log 44 statements and use logcat to view them. The beginning and end of every tests is automatically logged
|
/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/tools/aapt/ |
D | Android.mk | 51 tests/AaptConfig_test.cpp \ 52 tests/AaptGroupEntry_test.cpp \ 53 tests/Pseudolocales_test.cpp \ 54 tests/ResourceFilter_test.cpp \ 55 tests/ResourceTable_test.cpp
|
/frameworks/support/app-toolkit/ |
D | settings.gradle | 42 include ':paging:integration-tests:testapp' 43 project(':paging:integration-tests:testapp').projectDir = new File(supportRoot, "paging/integration… 66 include ':lifecycle:integration-tests:testapp' 67 project(':lifecycle:integration-tests:testapp').projectDir = new File(supportRoot, "lifecycle/integ… 93 include ':room:integration-tests:testapp' 94 project(':room:integration-tests:testapp').projectDir = new File(supportRoot, "room/integration-tes… 96 include ':room:integration-tests:kotlintestapp' 97 project(':room:integration-tests:kotlintestapp').projectDir = new File(supportRoot, "room/integrati…
|
/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()
|
D | TestGroupingTest.java | 42 List<TestMethod> tests = mGrouping.getTests(); in testGetTests_noPublicConstructor() local 44 assertEquals(1, tests.size()); in testGetTests_noPublicConstructor() 45 assertEquals("testPublicConstructor", tests.get(0).getName()); in testGetTests_noPublicConstructor()
|
/frameworks/native/cmds/dumpstate/ |
D | Android.mk | 9 LOCAL_COMPATIBILITY_SUITE := device-tests 10 LOCAL_MODULE_TAGS := tests 18 tests/dumpstate_test_fixture.cpp 20 LOCAL_TEST_DATA := $(call find-test-data-in-subdirs, $(LOCAL_PATH), *, tests/testdata)
|
/frameworks/opt/net/lowpan/libandroid_net_lowpan/tests/ |
D | README.md | 2 This package contains unit tests for libandroid_net_lowpan based on the 8 The easiest way to run tests is simply run 11 frameworks/opt/net/lowpan/libandroid_net_lowpan/tests/runtests.sh 15 connected device. It will then run the tests on the device. 27 See below for a few examples 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/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/base/core/tests/coretests/ |
D | README | 18 The Android platform core tests (APCT) consist of unit tests for core platform 25 To run a test or set of tests, first build the FrameworksCoreTests package: 29 Next, install the resulting APK and run tests as you would normal JUnit tests: 35 To run a tests within a specific package, add the following argument AFTER -w: 44 To run tests in debug mode:
|
/frameworks/rs/script_api/ |
D | generate.sh | 40 rm -f ../../../cts/tests/tests/renderscript/src/android/renderscript/cts/generated/* 41 mv test/* ../../../cts/tests/tests/renderscript/src/android/renderscript/cts/generated/ 52 mv slangtest/all$i.rs ../../compile/slang/tests/P_all_api_$i
|
/frameworks/rs/tests/java_api/RSUnitTests/src/com/android/rs/unittest/ |
D | single_source_ref_count.rs | 67 } tests[] = { 76 for (int i = 0; tests[i].fp; i++) { 77 rsDebug(tests[i].name, 0); 78 rs_allocation allocation = tests[i].fp();
|
/frameworks/av/media/libaaudio/scripts/ |
D | convert_oboe_aaudio.sh | 11 OBOETEST_DIR=${ANDROID_BUILD_TOP}/cts/tests/tests/nativemedia/aaudio/src/ 46 mv ${LIBOBOE_DIR}/tests/test_oboe_api.cpp ${LIBOBOE_DIR}/tests/test_aaudio_api.cpp
|
/frameworks/rs/rsov/compiler/tests/ |
D | lit.cfg | 13 # testFormat: The test format to use to interpret tests. 23 # test_source_root: The path where tests are located (default is the test suite 26 # test_exec_root: The root path where tests should be run. 27 config.test_exec_root = os.path.join(ANDROID_HOST_OUT, 'tests', 'rs2spirv')
|
/frameworks/rs/tests/java_api/RSUnitTests/supportlibsrc_gen/com/android/rs/unittest/ |
D | single_source_ref_count.rs | 69 } tests[] = { 78 for (int i = 0; tests[i].fp; i++) { 79 rsDebug(tests[i].name, 0); 80 rs_allocation allocation = tests[i].fp();
|
/frameworks/base/tools/preload2/src/com/android/preload/classdataretrieval/jdwp/ |
D | JDWPClassDataRetriever.java | 22 import org.apache.harmony.jpda.tests.framework.jdwp.CommandPacket; 23 import org.apache.harmony.jpda.tests.framework.jdwp.JDWPCommands; 24 import org.apache.harmony.jpda.tests.framework.jdwp.JDWPConstants; 25 import org.apache.harmony.jpda.tests.framework.jdwp.ReplyPacket; 26 import org.apache.harmony.jpda.tests.jdwp.share.JDWPTestCase; 27 import org.apache.harmony.jpda.tests.jdwp.share.JDWPUnitDebuggeeWrapper; 28 import org.apache.harmony.jpda.tests.share.JPDALogWriter; 29 import org.apache.harmony.jpda.tests.share.JPDATestOptions;
|
/frameworks/ml/nn/ |
D | README.txt | 32 e.g. runtime, driver, or tests. Includes source code and 40 /hardware/interfaces/neuralnetworks/*/vts: The VTS tests. 41 /test/vts-testcase/hal/neuralnetworks: Configuration for the VTS tests 47 /cts/tests/tests/ml/nn: The CTS tests
|
/frameworks/rs/tests/java_api/RSUnitTests/ |
D | RSUnitTests.py | 193 tests = [] 196 tests.extend(tests_for_version) 197 tests = sorted(tests) 204 for test in tests: 291 for _, tests in UNIT_TESTS.iteritems(): 292 ret.update(tests) 594 tests = sorted(UNIT_TESTS[version]) 598 for test in tests:
|