| /frameworks/base/docs/html/guide/topics/testing/ |
| D | index.jd | 17 Activity Testing</a> focuses on testing activities. It describes how instrumentation allows
18 you to control activities outside the normal application lifecycle. It also lists
24 Content Provider Testing</a> focuses on testing content providers. It describes the
30 Service Testing</a> focuses on testing services. It also lists service-specific features
35 is an overview of the types of testing you should do. It focuses on testing
82 sample application. It provides a simple example of unit
|
| D | activity_testing.jd | 132 infrastructure. It runs the Activities in a normal instance of the application under test,
133 using a standard system Context. It allows you to send mock Intents to the activity under
153 It invokes {@link junit.framework.TestCase#setUp() setUp()} and
155 method call. It does not allow you to inject any mock objects.
159 <code>standard</code>. It ensures that the test fixture is not reset between tests. You
243 It guides you through a more complex testing scenario that you develop against a
|
| /frameworks/base/libs/usb/tests/AccessoryChat/ |
| D | README.txt | 1 This is a test app for the USB accessory APIs. It consists of two parts:
8 It builds both for the host (Linux PC) and as an android
|
| /frameworks/base/core/java/android/ddm/ |
| D | README.txt | 3 It's not necessary to put all DDM-related code in this package; this just
|
| /frameworks/base/opengl/specs/ |
| D | EGL_ANDROID_recordable.txt | 99 RESOLVED: It should be a new attribute. It does not make sense to use up a
104 RESOLVED: It should not affect sorting. Some implementations may not have
|
| /frameworks/base/docs/html/guide/basics/ |
| D | building-blocks.jd | 10 <p>Generally, these components all run in the same system process. It's
29 can include displaying a UI to the user. It doesn't have to, though - some
53 <dd>A Service is a body of code that runs in the background. It can run in
|
| /frameworks/base/docs/html/guide/developing/tools/ |
| D | hierarchy-viewer.jd | 7 interface. It provides a visual representation of the layout's View hierarchy
|
| /frameworks/base/media/libstagefright/codecs/on2/h264dec/omxdl/arm11/ |
| D | ARM_DELIVERY.TXT | 4 It contains the ARM data versions listed below.
40 It should be noted that Support for the Beta release of the deliverable
|
| /frameworks/base/media/libstagefright/codecs/on2/h264dec/omxdl/reference/ |
| D | ARM_DELIVERY.TXT | 4 It contains the ARM data versions listed below.
40 It should be noted that Support for the Beta release of the deliverable
|
| /frameworks/base/media/libstagefright/codecs/on2/h264dec/omxdl/arm_neon/ |
| D | ARM_DELIVERY.TXT | 4 It contains the ARM data versions listed below.
40 It should be noted that Support for the Beta release of the deliverable
|
| /frameworks/base/docs/html/resources/articles/ |
| D | layout-tricks-stubs.jd | 14 <p>A <code>ViewStub</code> is a dumb and lightweight view. It has no dimension,
76 <p>It is very important to remember that after the stub is inflated, the stub is
83 your view hierarchy, simply use a <code>ViewStub</code>. It's cheap and easy.
|
| D | painless-threading.jd | 14 It is also the thread where your application interacts with running
91 and more difficult to read. It becomes even worse when your implement
101 curiouscreature/android/shelves/util/UserTask.java">UserTask</a>. It offers the
124 it. It is also very important to remember that an <code>AsyncTask</code>
|
| /frameworks/base/docs/html/guide/topics/processes/ |
| D | process-lifecycle.jd | 15 <p>It is important that
47 <li> It is running an {@link android.app.Activity}
50 <li> It has a {@link android.content.BroadcastReceiver} that is currently running
53 <li>It has a {@link android.app.Service} that is currently executing code
|
| /frameworks/base/docs/html/guide/topics/wireless/ |
| D | index.jd | 11 It also provides information about all non-connected available networks. Some of the available netw…
|
| /frameworks/base/docs/html/guide/topics/manifest/ |
| D | permission-tree-element.jd | 17 ownership of all names within the tree. It can dynamically add new permissions
48 <dd>The name that's at the base of the permission tree. It serves as
|
| D | manifest-intro.jd | 31 <li>It names the Java package for the application.
34 <li>It describes the components of the application — the activities,
36 composed of. It names the classes that implement each of the components and
41 <li>It determines which processes will host application components.</li>
43 <li>It declares which permissions the application must have in order to
46 <li>It also declares the permissions that others are required to have in
49 <li>It lists the {@link android.app.Instrumentation} classes that provide
54 <li>It declares the minimum level of the Android API that the application
57 <li>It lists the libraries that the application must be linked against.</li>
191 element is the exception to this rule: It must follow the
[all …]
|
| D | intent-filter-element.jd | 31 of broadcasts a receiver can handle. It opens the component to receiving
102 <li>It provides information about how able an activity is to respond to
108 <li><p>It controls the order in which broadcast receivers are executed to
|
| /frameworks/base/docs/html/guide/tutorials/views/ |
| D | hello-spinner.jd | 7 It is similar to a dropdown list and will allow scrolling when the
96 <p>It should look like this:</p>
|
| /frameworks/base/opengl/tests/angeles/ |
| D | README.txt | 10 Assembly'2004 event. It won the first place in the 4 KB intro
17 The original version was made for desktop with OpenGL. It was
|
| /frameworks/base/docs/html/guide/developing/debugging/ |
| D | debugging-devtools.jd | 34 <li>It will prevent Android from throwing an error if you pause on a breakpoint for a long
37 <li>It will enable you to select the <em>Wait for Debugger</em> option to pause application
|
| /frameworks/base/docs/html/guide/topics/graphics/ |
| D | animation.jd | 44 works the way you want, there is no need to use the property animation system. It also might
56 <dd>View Animation is the older system and can only be used for Views. It is relatively easy to
|
| /frameworks/base/docs/html/guide/appendix/ |
| D | glossary.jd | 42 SDK. It provides tools to browse the device, copy tools on the device, and
58 a Bitmap or Surface object. It has methods for standard computer drawing
91 with the SDK. It provides screen capture, log dump, and process
122 {@link android.content.Intent}. It includes several criteria fields that you can
182 complex 3D images. It is harder to use than a Canvas object, but
248 windows, and so on). It receives calls from its parent object (see
274 <dd> A panel is a concept not backed by a specific class. It is a View of
|
| /frameworks/base/docs/html/guide/topics/intents/ |
| D | intents-filters.jd | 44 activity to do something new. (It can also be passed to
52 connection between the calling component and a target service. It can optionally
74 This document begins with a description of Intent objects. It then describes the
85 An {@link android.content.Intent} object is a bundle of information. It
344 to the broadcast announcement. It does so by comparing the contents of
375 the component is willing to receive. It, in effect, filters in
570 of the data. It's more common in filters than a URI. Both the Intent object and
594 type matches a type listed in the filter. It passes the URI part of the test
638 the user follows a link on a web page. It first tries to display the data
672 (as illustrated in the previous section). It then displays the icons and
[all …]
|
| /frameworks/base/tools/orientationplot/ |
| D | README.txt | 69 between sensor events as reported by the SensorEvent.timestamp field. It
79 5. Each orientation has its own bound on allowable tilt angles. It's a good idea to
|
| /frameworks/base/docs/html/resources/tutorials/testing/ |
| D | helloandroid_test.jd | 71 …It guides you through the process of setting up a test project, adding a test, and running the tes…
162 <code>HelloAndroidTest</code>: This defines the constructor for the class. It is
175 same as what is contained in the application's string resources. It is an example of
233 Open <code>HelloAndroidTest.java</code>. It should look like this:
255 It calls the super constructor with parameters that tell the framework what Android application
309 It's similar to <code>setUp()</code>, but with less overhead, since it only runs once.
505 It guides you through a more complex testing scenario that you develop against a
|