Home
last modified time | relevance | path

Searched refs:coverage (Results 1 – 25 of 29) sorted by relevance

12

/packages/services/Telecomm/scripts/
Dtelecom_testing.sh23 local coverage=false
44 coverage=true;;
79 if [ $coverage = true ] ; then
121 if [ $coverage = true ] && [ $project =~ "telecom" ] ; then
127 if [ $coverage = true ] && [ $project =~ "telecom" ] ; then
130 adb pull /data/user/0/com.android.server.telecom.tests/files/coverage.ec /tmp/
137 --coverage-file "/tmp/coverage.ec" \
/packages/providers/CalendarProvider/tests/
DEMMA_README2 # the Calendar provider with EMMA coverage, executes the Calendar CTS
25 # rebuild provider with emma coverage
33 adb shell am instrument -w -e coverage true \
44 adb pull $output coverage.ec
47 emma report -r html -in coverage.ec \
49 … -in ${ANDROID_BUILD_TOP}/out/target/common/obj/APPS/CalendarProvider_intermediates/coverage.em
59 # rebuild provider without emma coverage
/packages/modules/Wifi/service/tests/wifitests/
DREADME.md24 If you would like to collect code coverage information you can run the `coverage.sh` script located
25 in this directory. It will rebuild parts of your tree with coverage enabled and then run the tests,
32 frameworks/opt/net/wifi/tests/wifitests/coverage.sh wifi_coverage
Dcoverage.sh51 REMOTE_COVERAGE_OUTPUT_FILE=/data/data/com.android.server.wifi.test/files/coverage.ec
87 adb shell am instrument -e coverage true --no-hidden-api-checks \
97 --name wifi-coverage \
/packages/modules/DnsResolver/tests/
DAndroid.bp119 // However, MTS coverage requires 32 bit test binary to run.
128 // TODO: Remove resolv_test_mts_coverage_defaults after mts coverage switched to 64-bit device.
192 // multilib setting is worth because we might be able to get some coverage for the case where
213 // TODO: Remove resolv_test_mts_coverage_defaults after mts coverage switched to 64-bit device.
/packages/apps/ManagedProvisioning/tools/bash/
Dcoverage.sh61 adb shell am instrument -e coverage true -e size small -w "$TEST_RUNNER"
70 --coverage-file "$COVERAGE_OUTPUT_FILE" \
/packages/apps/ManagedProvisioning/tests/
DREADME10 To obtain a test coverage report for instrumentation tests:
11 $ packages/apps/ManagedProvisioning/tools/bash/coverage.sh
/packages/providers/CallLogProvider/
DAndroid.bp23 // The Jacoco tool analyzes code coverage when running unit tests on the
26 // would dilute the coverage results. These options do not affect regular
/packages/providers/ContactsProvider/
DAndroid.bp37 // The Jacoco tool analyzes code coverage when running unit tests on the
40 // would dilute the coverage results. These options do not affect regular
/packages/providers/CalendarProvider/
DAndroid.bp52 // The Jacoco tool analyzes code coverage when running unit tests on the
55 // would dilute the coverage results. These options do not affect regular
/packages/modules/Connectivity/Tethering/tests/integration/
DAndroid.bp98 // Special version of the tethering tests that includes all tests necessary for code coverage
111 "modules-utils-native-coverage-listener",
/packages/modules/NetworkStack/tests/integration/
DAndroid.bp107 // Special version of the network stack tests that includes all tests necessary for code coverage
118 "modules-utils-native-coverage-listener",
/packages/apps/Messaging/src/com/android/messaging/datamodel/
DBugleNotifications.java154 public static void update(final boolean silent, final int coverage) { in update() argument
155 update(silent, null /* conversationId */, coverage); in update()
168 final int coverage) { in update() argument
172 + " coverage = " + coverage); in update()
184 if ((coverage & UPDATE_MESSAGES) != 0) { in update()
188 if ((coverage & UPDATE_ERRORS) != 0) { in update()
/packages/modules/DnsResolver/
DAndroid.bp135 // This is necessary to have the coverage tests run on cf_x86_phone.
137 // suite on cf_x86_phone (32-bit) for coverage.
139 // TODO: Remove this target after coverage test switched to 64-bit device.
/packages/modules/Connectivity/tests/common/
DAndroid.bp46 // Connectivity coverage tests combines Tethering and Connectivity tests, each with their
82 "modules-utils-native-coverage-listener",
/packages/apps/Car/libs/car-ui-lib/
DREADME.md52 ### Getting coverage reports
54 …eport under `packages/apps/Car/libs/car-ui-lib/car-ui-lib/build/reports/coverage/debug/index.html`…
/packages/modules/Connectivity/
DTEST_MAPPING6 // some latest APIs. Run CtsNetTestCases to get coverage of newer APIs.
/packages/apps/ManagedProvisioning/
DAndroid.bp102 // Packages to be included in code coverage runs. This does not affect production builds.
/packages/apps/CellBroadcastReceiver/tests/unit/
DAndroid.bp78 // used to run mts coverage test
/packages/apps/Test/connectivity/sl4n/rapidjson/
DCHANGELOG.md34 * 100% [Coverall](https://coveralls.io/r/miloyip/rapidjson?branch=master) coverage.
/packages/modules/Connectivity/Tethering/tests/unit/
DAndroid.bp82 // Library containing the unit tests. This is used by the coverage test target to pull in the
/packages/modules/NetworkStack/tests/unit/
DAndroid.bp69 // Library containing the unit tests. This is used by the coverage test target to pull in the
/packages/modules/IPsec/
DAndroid.bp118 // being overwritten by the frameworks class copies and break code coverage
/packages/modules/NeuralNetworks/runtime/test/android_fuzzing/
DREADME.md9 `libFuzzer`, which are efficient at fuzzing because they use line coverage of
58 `libFuzzer` can use the coverage from the driver to guide the test
/packages/modules/NeuralNetworks/runtime/test/
DAndroid.bp81 // library to ensure CTS tests coverage.

12