Searched defs:failures (Results 1 - 4 of 4) sorted by relevance

/frameworks/base/test-runner/tests/src/android/test/suitebuilder/
H A DInstrumentationTestSuiteBuilderTest.java76 private Set<String> failures = new HashSet<String>(); field in class:InstrumentationTestSuiteBuilderTest.SuiteExecutionRecorder
85 failures.add(testName(test));
100 return failures.contains(testName);
H A DUnitTestSuiteBuilderTest.java69 private Set<String> failures = new HashSet<String>(); field in class:UnitTestSuiteBuilderTest.SuiteExecutionRecorder
78 failures.add(testName(test));
93 return failures.contains(testName);
H A DTestSuiteBuilderTest.java178 private Set<String> failures = new HashSet<String>(); field in class:TestSuiteBuilderTest.SuiteExecutionRecorder
187 failures.add(testName(test));
202 return failures.contains(testName);
/frameworks/compile/mclinker/utils/gtest/src/
H A Dgtest-all.cpp120 // failure is reported. It can either intercept only failures that are
122 // all generated failures. The scope of this mock object can be controlled with
129 INTERCEPT_ONLY_CURRENT_THREAD, // Intercepts only thread local failures.
130 INTERCEPT_ALL_THREADS // Intercepts all failures.
135 // results. This reporter will only catch failures generated in the current
189 // to generate Google Test fatal failures. It verifies that the given
194 // affects and considers failures generated in the current thread and
246 // generate Google Test non-fatal failures. It asserts that the given
251 // affects and considers failures generated in the current thread and
1500 " should catch exceptions and treat them as test failures
4551 int failures = 0; local
[all...]

Completed in 407 milliseconds