| /frameworks/base/tests/backup/ |
| D | backup_stress_test.sh | 18 failures=0
45 failures=$(($failures+1))
47 echo "FAILED iteration $i of $iterations; $failures failures so far"
48 echo "FAILED iteration $i of $iterations; $failures failures so far" > /dev/stderr
58 echo "DONE: $iterations iterations with $failures failures."
59 echo "DONE: $iterations iterations with $failures failures." > /dev/stderr
60 [ "$failures" -eq 0 ] && exit 0
|
| /frameworks/base/media/tests/SoundPoolTest/src/com/android/ |
| D | SoundPoolTest.java | 337 int failures = 0; in run() local
351 if (!TestSounds()) failures = failures + 1; in run()
352 if (!TestScales()) failures = failures + 1; in run()
353 if (!TestRates()) failures = failures + 1; in run()
354 if (!TestPriority()) failures = failures + 1; in run()
355 if (!TestVolume()) failures = failures + 1; in run()
359 if (!TestPauseResume()) failures = failures + 1; in run()
363 failures = failures + 1; in run()
376 if (failures == 0) { in run()
379 Log.i(LOG_TAG, failures + " tests failed"); in run()
|
| /frameworks/base/test-runner/tests/src/android/test/suitebuilder/ |
| D | UnitTestSuiteBuilderTest.java | 69 private Set<String> failures = new HashSet<String>(); field in UnitTestSuiteBuilderTest.SuiteExecutionRecorder
78 failures.add(testName(test)); in addFailure()
93 return failures.contains(testName); in failed()
|
| D | InstrumentationTestSuiteBuilderTest.java | 76 private Set<String> failures = new HashSet<String>(); field in InstrumentationTestSuiteBuilderTest.SuiteExecutionRecorder
85 failures.add(testName(test)); in addFailure()
100 return failures.contains(testName); in failed()
|
| D | TestSuiteBuilderTest.java | 178 private Set<String> failures = new HashSet<String>();
187 failures.add(testName(test));
202 return failures.contains(testName);
|
| /frameworks/base/tools/apilint/ |
| D | apilint.py | 240 failures = {} variable
244 global failures
249 failures[sig] = Failure(sig, clazz, detail, error, rule, msg)
996 global failures
997 failures = {}
999 return failures
1004 global failures
1005 failures = {}
1008 return failures
1013 global failures
[all …]
|
| /frameworks/compile/slang/lit-tests/ |
| D | README | 18 When debugging failures, the "-v" option will print to stdout the details of
37 -v enables additional verbosity (useful when examining unexpected failures)
|
| /frameworks/opt/setupwizard/tools/gradle/ |
| D | android.properties | 9 // Redirect lint output so that failures appear in build server error logs
|
| /frameworks/compile/libbcc/tests/debuginfo/host-tests/ |
| D | lit.cfg | 23 # the target triple string that must be used in cases marked expected failures
|
| /frameworks/opt/telephony/src/java/com/android/internal/telephony/ |
| D | EventLogTags.logtags | 21 # PDP Setup failures
|
| /frameworks/compile/libbcc/tests/debuginfo/ |
| D | README | 58 -v enables additional verbosity (useful when examining unexpected failures)
|
| /frameworks/compile/libbcc/tests/debuginfo/target-tests/ |
| D | lit.cfg | 43 # the target triple string that must be used in cases marked expected failures
|
| /frameworks/base/docs/html/tools/testing/ |
| D | testing_eclipse.jd | 495 Number of failures (Failures:) - the number of test failures encountered during the test
496 run. This is the number of assertion failures. A test can fail even if the program does
|
| D | activity_test.jd | 941 … Number of failures (<em>Failures:</em>) - the number of test failures encountered during the test
942 …run. This is the number of assertion failures. A test can fail even if the program does not encoun…
1010 …the number of failures is 2, and small "x" icons appear in the list icons next to the testPreCondi…
1017 You now want to look at the failures to see exactly where they occurred.
1020 To examine the failures, follow these steps:
|
| D | testing_android.jd | 536 was run. You also see all the assertion failures that occurred. These include pointers to the
537 line in the test code where the failure occurred. Assertion failures also list the expected
|
| D | activity_testing.jd | 338 This section lists some of the common test failures you may encounter in UI testing, and their
|
| /frameworks/base/docs/html/about/versions/ |
| D | android-1.1.jd | 173 <li>Improves recovery from POP3 connection failures.</li>
|
| /frameworks/base/docs/html/training/activity-testing/ |
| D | activity-basic-testing.jd | 217 <li>In the JUnit view, verify that the test passes with no errors or failures.</li>
|
| /frameworks/base/docs/html/training/id-auth/ |
| D | authenticate.jd | 161 are expected to handle these failures automatically.</p>
|
| /frameworks/base/docs/html/guide/topics/security/ |
| D | permissions.jd | 146 will not receive an exception if there are permission failures. In almost all
151 each of the requested permissions. So you generally don't need to worry about runtime failures
|
| /frameworks/base/docs/html/ndk/guides/ |
| D | cpp-support.jd | 212 The failures are mostly in the areas of {@code wchar_t} and locales that Android bionic
|
| /frameworks/base/docs/html/guide/practices/ |
| D | verifying-apps-art.jd | 185 This can lead to CheckJNI failures because of the unhandled exceptions or the
|
| /frameworks/base/docs/html/training/articles/ |
| D | perf-jni.jd | 594 <p>Another class of <code>UnsatisfiedLinkError</code> failures looks like:</p>
638 <p>(Most of this advice applies equally well to failures to find methods
|
| /frameworks/base/docs/html/tools/building/ |
| D | manifest-merge.jd | 296 <p class="note"><strong>Note:</strong> Unresolved placeholder names in apps cause build failures.
|
| /frameworks/base/docs/html/training/testing/ui-testing/ |
| D | uiautomator-testing.jd | 326 element (for example, icons in a toolbar). Text selectors are brittle and can lead to test failures
|