| /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 | 325 int failures = 0; in run() local
339 if (!TestSounds()) failures = failures + 1; in run()
340 if (!TestScales()) failures = failures + 1; in run()
341 if (!TestRates()) failures = failures + 1; in run()
342 if (!TestPriority()) failures = failures + 1; in run()
343 if (!TestVolume()) failures = failures + 1; in run()
347 if (!TestPauseResume()) failures = failures + 1; in run()
351 failures = failures + 1; in run()
364 if (failures == 0) { in run()
367 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/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/base/core/tests/overlaytests/ |
| D | runtests.sh | 21 failures=0
|
| /frameworks/base/test-runner/src/junit/textui/ |
| D | ResultPrinter.java | 52 printDefects(result.failures(), result.failureCount(), "failure"); in printFailures()
|
| /frameworks/base/telephony/java/com/android/internal/telephony/ |
| D | EventLogTags.logtags | 21 # PDP Setup failures
|
| /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/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 | 954 … Number of failures (<em>Failures:</em>) - the number of test failures encountered during the test
955 …run. This is the number of assertion failures. A test can fail even if the program does not encoun…
1023 …the number of failures is 2, and small "x" icons appear in the list icons next to the testPreCondi…
1030 You now want to look at the failures to see exactly where they occurred.
1033 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 | 172 <li>Improves recovery from POP3 connection failures.</li>
|
| D | android-2.3.jd | 235 and retrying downloads after failures or across connectivity changes and system
|
| /frameworks/base/docs/html/training/id-auth/ |
| D | authenticate.jd | 161 are expected to handle these failures automatically.</p>
|
| /frameworks/compile/mclinker/utils/gtest/ |
| D | README | 13 failures, various options for running the tests, and XML test report
|
| /frameworks/base/docs/html/guide/topics/security/ |
| D | permissions.jd | 145 will not receive an exception if there are permission failures. In almost all
|
| /frameworks/compile/mclinker/utils/gtest/src/ |
| D | gtest-all.cpp | 4551 int failures = 0; in OutputXmlTestInfo() local
4555 if (++failures == 1) in OutputXmlTestInfo()
4569 if (failures == 0) in OutputXmlTestInfo()
|
| /frameworks/base/docs/html/guide/practices/app-design/ |
| D | jni.jd | 590 <p>Another class of <code>UnsatisfiedLinkError</code> failures looks like:</p>
|
| /frameworks/base/docs/html/guide/practices/ |
| D | jni.jd | 590 <p>Another class of <code>UnsatisfiedLinkError</code> failures looks like:</p>
|
| /frameworks/base/docs/html/guide/topics/media/jet/ |
| D | jetcreator_manual.jd | 127 score of successes and failures. JET allows for these types of music driven
|