Home	Sort by relevance Sort by last modified time

Full Search Definition Symbol File Path History   | | Help

    Searched full:cases (Results 401 - 425 of 4969) sorted by null

<<11121314151617181920>>

/external/webkit/Source/WebCore/platform/graphics/
FloatRect.cpp	71 // Return a clean empty rectangle for non-intersecting cases. 84 // Handle empty special cases first. 102 // Handle empty special cases first.
/frameworks/base/docs/html/training/monitoring-device-state/
battery-monitoring.jd	36 is negligible, so in most cases you can maximize your refresh rate whenever the device is connected 116 <p>In some cases it's also useful to determine the current battery level. You may choose to reduce 153 <p>In many cases, the act of charging a device is coincident with putting it into a dock. The next
/bionic/libm/man/
lround.3	59 rounding away from zero in halfway cases.
/bionic/libm/src/
e_acosh.c	28 * Special cases:
e_atanh.c	30 * Special cases:
/dalvik/dx/src/com/android/dx/cf/code/
BytecodeArray.java	838 SwitchList cases = new SwitchList(count); local 875 SwitchList cases = new SwitchList(npairs); local     [all...]
/development/pdk/docs/porting/
instrumentation_testing.jd	20 <p>This document describes how to use the Instrumentation Framework to write test cases. Instrumentation testing allows you to verify a particular feature or behavior with an automated JUnit TestCase. You can launch activities and providers within an application, send key events, and make assertions about various UI elements. </p> 28 <p> Each Android application runs in its own process. Instrumentation kills the application process and restarts the process with Instrumentation. Instrumentation gives a handle to the application context used to poke around the application to validate test assertions, allowing you to write test cases to test applications at a much lower level than UI screen shot tests. Note that Instrumentation cannot catch UI bugs. </p> 49 <td valign="top">The instrumentation test runner is an instrumentation that runs instrumentation test cases and injects itself into each test case. Instrumentation test cases need to be grouped together with an instrumentation test runner with the appropriate target package.</td> 100 <p>This section provides an overview for various unit and functional test cases that can be executed through the instrumentation framework.</p> 105 <p>Framework test cases test the Android application framework or specific Android application functionality that requires an Android runtime context. These tests can be found in <code>//device/tests</code> and <code>//device/apps/AndroidTests</code>.</p> 110 <p>Core library test cases test the Android library functionality that does not require an Android runtime context. These tests are split into Android library (android.* package space) tests at <code>//device/java/tests</code> and Java library (java.*, javax.*, etc. packages) tests at <code>//device/dalvik/libcore/.../tests</code>.</p> 123 <li> <code>make Contactstests</code>: Compiles the test cases. </li> 486 <p>If you run your test cases and nothing appears to happen, have a look at <code>adb logcat</code>. The following is a common problem:</p>
/development/samples/ApiDemos/src/com/example/android/apis/view/
HoverInterceptorView.java	35 * hover events. This can be useful in some cases when implementing a custom
/development/samples/NotePad/tests/
AndroidManifest.xml	34 code for test cases.
/development/samples/SpinnerTest/
AndroidManifest.xml	33 which is needed when building test cases.
/development/tools/a3dconvert/
ColladaGeometry.h	61 // different size in the cases the same vertex produces divergent normals for different faces
/docs/source.android.com/src/compatibility/
contact-us.md	35 cases that require disclosure of confidential information only, so general
/external/apache-harmony/security/src/test/api/java/org/apache/harmony/security/tests/java/security/
CodeSignerTest.java	82 // special cases
/external/bluetooth/bluez/test/
bdaddr.8	23 specified by the -t flag. In both cases, the device must be reset before the
/external/bluetooth/glib/tests/
utf8.txt	9 # Beyond that, this file consists of a series of test cases. Each test case consists of
/external/chromium/base/debug/
leak_tracker_unittest.cc	70 // Try some orderings of create/remove to hit different cases in the linked-list
/external/chromium/base/
file_descriptor_shuffle.h	12 // handle the edge cases (like mapping 0 -> 1, 1 -> 0) correctly.
/external/chromium/chrome/browser/
browser_about_handler.h	35 // dialogs. This function handles those cases, and returns true if so. In this
/external/chromium/chrome/browser/policy/
policy_path_parser.h	19 // existing used cases.
/external/chromium/chrome/browser/resources/options/
clear_browser_data_overlay.js	95 // cases.
/external/chromium/chrome/browser/rlz/
rlz.h	48 // Returns false if the rlz string could not be obtained. In some cases
/external/chromium/chrome/browser/ui/cocoa/applescript/
tab_applescript.h	25 // when it calls insertInTabs: of a particular window, it is used in cases
/external/chromium/chrome/browser/ui/cocoa/
bubble_view.h	36 // The window from which we get the theme used to draw. In some cases,
/external/chromium/chrome/browser/ui/toolbar/
encoding_menu_controller_unittest.cc	40 // ones so we'll catch such cases.
/external/chromium/chrome/browser/ui/views/
unhandled_keyboard_event_handler.cc	26 // cases, we discard the Char events.

Completed in 546 milliseconds

<<11121314151617181920>>