/frameworks/base/core/tests/coretests/src/android/widget/ |
D | AutoCompleteTextViewCallbacks.java | 39 final Instrumentation instrumentation = getInstrumentation(); in testPopupNoSelection() local 43 instrumentation.waitForIdleSync(); in testPopupNoSelection() 45 instrumentation.waitForIdleSync(); in testPopupNoSelection() 64 final Instrumentation instrumentation = getInstrumentation(); in testPopupEnterSelection() local 68 instrumentation.waitForIdleSync(); in testPopupEnterSelection() 79 instrumentation.waitForIdleSync(); in testPopupEnterSelection() 97 instrumentation.waitForIdleSync(); in testPopupEnterSelection() 113 final Instrumentation instrumentation = getInstrumentation(); in testPopupLeaveSelection() local 117 instrumentation.waitForIdleSync(); in testPopupLeaveSelection() 119 instrumentation.waitForIdleSync(); in testPopupLeaveSelection() [all …]
|
D | AutoCompleteTextViewPopup.java | 48 final Instrumentation instrumentation = getInstrumentation(); in testPopupSetListSelection() local 52 instrumentation.waitForIdleSync(); in testPopupSetListSelection() 64 instrumentation.waitForIdleSync(); in testPopupSetListSelection() 80 final Instrumentation instrumentation = getInstrumentation(); in testPopupGetListSelection() local 84 instrumentation.waitForIdleSync(); in testPopupGetListSelection() 107 final Instrumentation instrumentation = getInstrumentation(); in testPopupClearListSelection() local 111 instrumentation.waitForIdleSync(); in testPopupClearListSelection() 127 instrumentation.waitForIdleSync(); in testPopupClearListSelection() 140 final Instrumentation instrumentation = getInstrumentation(); in testPopupNavigateNoAdapter() local 144 instrumentation.waitForIdleSync(); in testPopupNavigateNoAdapter() [all …]
|
/frameworks/base/core/java/android/test/ |
D | InstrumentationTestCase.java | 46 public void injectInstrumentation(Instrumentation instrumentation) { in injectInstrumentation() argument 47 mInstrumentation = instrumentation; in injectInstrumentation() 60 public void injectInsrumentation(Instrumentation instrumentation) { in injectInsrumentation() argument 61 injectInstrumentation(instrumentation); in injectInsrumentation() 251 final Instrumentation instrumentation = getInstrumentation(); in sendKeys() local 274 instrumentation.sendKeyDownUpSync(keyCode); in sendKeys() 290 instrumentation.waitForIdleSync(); in sendKeys() 301 final Instrumentation instrumentation = getInstrumentation(); in sendKeys() local 305 instrumentation.sendKeyDownUpSync(keys[i]); in sendKeys() 313 instrumentation.waitForIdleSync(); in sendKeys() [all …]
|
/frameworks/base/test-runner/src/android/test/ |
D | AndroidTestRunner.java | 185 Test test, Instrumentation instrumentation) { in setInstrumentationIfInstrumentationTestCase() argument 187 ((InstrumentationTestCase) test).injectInstrumentation(instrumentation); in setInstrumentationIfInstrumentationTestCase() 198 public void setInstrumentation(Instrumentation instrumentation) { in setInstrumentation() argument 199 mInstrumentation = instrumentation; in setInstrumentation() 207 public void setInstrumentaiton(Instrumentation instrumentation) { in setInstrumentaiton() argument 208 setInstrumentation(instrumentation); in setInstrumentaiton()
|
/frameworks/base/core/tests/coretests/src/android/util/ |
D | ListUtil.java | 37 public ListUtil(ListView listView, Instrumentation instrumentation) { in ListUtil() argument 39 mInstrumentation = instrumentation; in ListUtil()
|
/frameworks/base/core/java/android/content/pm/ |
D | PackageInfo.java | 123 public InstrumentationInfo[] instrumentation; field in PackageInfo 229 dest.writeTypedArray(instrumentation, parcelableFlags); in writeToParcel() 266 instrumentation = source.createTypedArray(InstrumentationInfo.CREATOR); in PackageInfo()
|
D | PackageParser.java | 322 int N = p.instrumentation.size(); in generatePackageInfo() 324 pi.instrumentation = new InstrumentationInfo[N]; in generatePackageInfo() 326 pi.instrumentation[i] = generateInstrumentationInfo( in generatePackageInfo() 327 p.instrumentation.get(i), flags); in generatePackageInfo() 1199 if (!foundApp && pkg.instrumentation.size() == 0) { in parsePackage() 1534 owner.instrumentation.add(a); in parseInstrumentation() 2939 public final ArrayList<Instrumentation> instrumentation = new ArrayList<Instrumentation>(0); field in PackageParser.Package 3043 for (int i=instrumentation.size()-1; i>=0; i--) { in setPackageName() 3044 instrumentation.get(i).setPackageName(newName); in setPackageName()
|
/frameworks/base/test-runner/tests/src/android/test/suitebuilder/examples/instrumentation/ |
D | InstrumentationTest.java | 17 package android.test.suitebuilder.examples.instrumentation;
|
/frameworks/base/core/java/android/app/ |
D | LoadedApk.java | 461 Instrumentation instrumentation) { in makeApplication() argument 490 if (instrumentation != null) { in makeApplication() 492 instrumentation.callApplicationOnCreate(app); in makeApplication() 494 if (!instrumentation.onException(app, e)) { in makeApplication() 556 Instrumentation instrumentation, boolean registered) { in getReceiverDispatcher() argument 568 instrumentation, registered); in getReceiverDispatcher() 750 Handler activityThread, Instrumentation instrumentation, in ReceiverDispatcher() argument 760 mInstrumentation = instrumentation; in ReceiverDispatcher()
|
/frameworks/base/docs/html/guide/topics/testing/ |
D | activity_testing.jd | 84 Activity testing is particularly dependent on the the Android instrumentation framework. 86 can't be invoked directly except by instrumentation. Also, the only way to send events to the 87 user interface from a program is through instrumentation. 90 This document describes how to test activities using instrumentation and other test 93 the introduction to the Android testing and instrumentation framework. 98 which provides instrumentation to the test case subclasses you use for Activities. 105 Lifecycle control: With instrumentation, you can start the activity under test, pause it, 115 User interface interaction: You use instrumentation to send keystrokes or touch events 261 This changes when you run tests against the application. With instrumentation-based classes, 375 Run the interaction on the UI thread. Use a test class that provides instrumentation. See
|
D | testing_android.jd | 222 The Android testing API is based on the JUnit API and extended with a instrumentation 251 … Android instrumentation is a set of control methods or "hooks" in the Android system. These hooks 262 methods directly, but you can do so using instrumentation. 271 With Android instrumentation, though, you can invoke callback methods in your test code. 302 part of the instrumentation API. The Activity under test is not started until you call this 307 Also, instrumentation can load both a test package and the application under test into the 360 If you want to use instrumentation methods in a test case class, you must use 489 manifest file, in the <a href="{@docRoot}guide/topics/manifest/instrumentation-element.html"> 490 instrumentation</a> element. Also, <code>InstrumentationTestRunner</code> code resides 500 <code>InstrumentationTestRunner</code>, you must change the <instrumentation> [all …]
|
D | index.jd | 17 Activity Testing</a> focuses on testing activities. It describes how instrumentation allows
|
D | service_testing.jd | 57 from its clients, you can test a Service object without using instrumentation. 64 the introduction to the Android testing and instrumentation framework.
|
D | contentprovider_testing.jd | 69 the introduction to the Android testing and instrumentation framework.
|
/frameworks/base/docs/html/resources/tutorials/testing/ |
D | activity_test.jd | 88 …instrumentation to give you control over your main application while you are testing it. The entir… 106 …extend JUnit and also connect you to the application under test with instrumentation. You can send… 124 …at the main UI operation works correctly. This test demonstrates the instrumentation features avai… 128 … the application's code for saving state. This test demonstrates the instrumentation features of t… 363 Also, the test application is already set up to use instrumentation. You can see this 375 <instrumentation 385 Notice the <code><instrumentation></code> element. The attribute 390 The <code><instrumentation></code> element also contains the attribute 392 instrumentation to run the test application with Android's instrumentation-enabled test runner. 413 It also demonstrates that with Android instrumentation you can look at the application [all …]
|
D | helloandroid_test.jd | 75 …If you'd like to read an overview of the test and instrumentation framework and the core test case… 489 <strong>Explore the Android instrumentation framework</strong> 495 is the base class for test case classes that use additional instrumentation features.
|
/frameworks/base/docs/html/guide/topics/manifest/ |
D | instrumentation-element.jd | 1 page.title=<instrumentation> 8 <dd><pre class="stx"><instrumentation android:<a href="#ftest">functionalTest</a>=["true" | "fal…
|
D | manifest-element.jd | 28 <dd><code><a href="{@docRoot}guide/topics/manifest/instrumentation-element.html"><instrumentatio…
|
D | manifest-intro.jd | 81 …<a href="{@docRoot}guide/topics/manifest/instrumentation-element.html"><instrumentation /></… 141 <br/><code><a href="{@docRoot}guide/topics/manifest/instrumentation-element.html"><instrumentati…
|
/frameworks/base/docs/html/guide/developing/testing/ |
D | testing_otheride.jd | 141 The operation also creates an <code>AndroidManifest.xml</code> file with instrumentation 143 are testing and control it with instrumentation. 159 instrumentation-related elements and attributes: 171 <code><instrumentation></code>: contains attributes that control Android 172 instrumentation. The attributes are: 177 JUnit test case runner classes and Android instrumentation classes. 189 user-readable label for the instrumentation class. By default, 261 classes also provide instrumentation for testing. 442 Forces <code>am instrument</code> to wait until the instrumentation terminates 471 <code>am instrument</code> tool passes these to the specified instrumentation class [all …]
|
D | testing_eclipse.jd | 35 <code><instrumentation></code> element in the test package's manifest file. 64 <a href="{@docRoot}guide/topics/manifest/instrumentation-element.html"> 65 <code><instrumentation></code></a> element in its manifest file. 70 <code><instrumentation></code> element in the manifest file. You can use the New 147 also provide instrumentation for testing an Activity. To learn more about test case 436 <code>Launching instrumentation <em>instrumentation_class</em> on device 440 instrumentation test runner you have specified (usually 468 [2010-01-01 12:45:02 - MyTest] Launching instrumentation android.test.InstrumentationTestRunner on …
|
/frameworks/base/test-runner/tests/src/android/test/suitebuilder/ |
D | UnitTestSuiteBuilderTest.java | 19 import android.test.suitebuilder.examples.instrumentation.InstrumentationTest;
|
D | InstrumentationTestSuiteBuilderTest.java | 21 import android.test.suitebuilder.examples.instrumentation.InstrumentationTest;
|
/frameworks/base/data/keyboards/ |
D | Virtual.kcm | 17 # for instrumentation and testing purposes.
|
/frameworks/base/docs/html/guide/developing/projects/ |
D | index.jd | 396 "{@docRoot}guide/topics/manifest/instrumentation-element.html"> 397 <code><instrumentation></code></a> 443 the instrumentation in that project. This lets you create a self-contained project that
|