HomeSort by relevance Sort by last modified time
    Searched full:instrumentation (Results 551 - 575 of 1688) sorted by null

<<21222324252627282930>>

  /frameworks/base/core/tests/coretests/apks/install_complete_package_info/
AndroidManifest.xml 31 <instrumentation
  /frameworks/base/core/tests/hosttests/test-apps/DownloadManagerTestApp/
AndroidManifest.xml 32 <instrumentation
  /frameworks/base/core/tests/hosttests/test-apps/DownloadManagerTestApp/src/com/android/frameworks/downloadmanagertests/
DownloadManagerTestRunner.java 29 * Instrumentation Test Runner for all download manager tests.
  /frameworks/base/graphics/tests/graphicstests/
AndroidManifest.xml 33 <instrumentation
  /frameworks/base/media/tests/MediaFrameworkTest/src/com/android/mediaframeworktest/
MediaFrameworkIntegrationTestRunner.java 30 * Instrumentation Test Runner for all media framework integration tests.
MediaFrameworkPerfTestRunner.java 30 * Instrumentation Test Runner for all MediaPlayer tests.
  /frameworks/base/media/tests/MediaFrameworkTest/src/com/android/mediaframeworktest/functional/audio/
SimTonesTest.java 28 * Junit / Instrumentation test case for the SIM tone generator
  /frameworks/base/nfc-extras/tests/
AndroidManifest.xml 35 <instrumentation android:name="android.test.InstrumentationTestRunner"
  /frameworks/base/sax/tests/saxtests/
AndroidManifest.xml 32 <instrumentation
  /frameworks/base/test-runner/tests/
AndroidManifest.xml 39 <instrumentation
  /frameworks/base/test-runner/tests/src/android/test/
InstrumentationTestRunnerTest.java 19 import android.app.Instrumentation;
108 assertTrue("Instrumentation did not finish", instrumentationTestRunner.isFinished());
111 Instrumentation.REPORT_KEY_STREAMRESULT);
112 assertTrue("Instrumentation results is missing RuntimeException",
  /frameworks/base/tests/CanvasCompare/
AndroidManifest.xml 43 <instrumentation
  /frameworks/base/tests/MemoryUsage/src/com/android/tests/memoryusage/
MemoryUsageTest.java 45 * The instrumentation expects the following key to be passed on the command line:
68 MemoryUsageInstrumentation instrumentation = local
70 Bundle args = instrumentation.getBundle();
88 instrumentation.sendStatus(0, results);
  /frameworks/base/tests/TtsTests/
AndroidManifest.xml 40 <instrumentation android:name="android.test.InstrumentationTestRunner"
  /packages/apps/Music/tests/src/com/android/music/
MusicPlayerNames.java 24 * in the instrumentation test.
  /external/chromium_org/chrome/tools/build/win/
syzygy_instrument.py 117 help='Specifies which instrumentation mode is to be used.')
124 'instrumentation executable.')
131 option_parser.error('You must provide an instrumentation mode.')
  /external/compiler-rt/lib/asan/tests/
CMakeLists.txt 5 # no-instrumentation tests.
8 # address sanitizer instrumentation pass. These tests form "integration" tests
10 # instrumentation against the just-built runtime library.
  /external/llvm/lib/Transforms/Instrumentation/
EdgeProfiling.cpp 21 #include "llvm/Transforms/Instrumentation.h"
50 "Insert instrumentation for edge profiling", false, false)
59 return false; // No main, no instrumentation!
  /external/llvm/test/Instrumentation/AddressSanitizer/
basic.ll 1 ; Test basic address sanitizer instrumentation.
19 ; First instrumentation block refines the shadow test.
52 ; First instrumentation block refines the shadow test.
  /external/valgrind/main/callgrind/
callgrind.h 110 /* Start full callgrind instrumentation if not already switched on.
118 /* Stop full callgrind instrumentation if not already switched off.
120 instrumentation afterwards, which effectivly will run at the same
  /external/valgrind/main/docs/xml/
manual-intro.xml 12 <para>Valgrind is an instrumentation framework for building dynamic analysis
79 some instrumentation basics; and <command>Nulgrind</command> is the minimal
80 Valgrind tool that does no analysis or instrumentation, and is only useful
  /frameworks/base/docs/html/tools/testing/
activity_testing.jd 80 Activity testing is particularly dependent on the Android instrumentation framework.
82 can't be invoked directly except by instrumentation. Also, the only way to send events to the
83 user interface from a program is through instrumentation.
86 This document describes how to test activities using instrumentation and other test
89 the introduction to the Android testing and instrumentation framework.
94 which provides instrumentation to the test case subclasses you use for Activities.
101 Lifecycle control: With instrumentation, you can start the activity under test, pause it,
105 Dependency injection: Instrumentation allows you to create mock system objects such as
111 User interface interaction: You use instrumentation to send keystrokes or touch events
242 This changes when you run tests against the application. With instrumentation-based classes
    [all...]
  /packages/apps/Camera/tests/src/com/android/camera/stress/
CameraStartUp.java 22 import android.app.Instrumentation;
52 Instrumentation inst = getInstrumentation();
75 Instrumentation inst = getInstrumentation();
  /packages/apps/Camera2/tests/src/com/android/camera/stress/
CameraStartUp.java 22 import android.app.Instrumentation;
52 Instrumentation inst = getInstrumentation();
75 Instrumentation inst = getInstrumentation();
  /packages/apps/LegacyCamera/tests/src/com/android/camera/stress/
CameraStartUp.java 23 import android.app.Instrumentation;
53 Instrumentation inst = getInstrumentation();
75 Instrumentation inst = getInstrumentation();

Completed in 337 milliseconds

<<21222324252627282930>>