Home | History | Annotate | Download | only in tests

Lines Matching full:code

3     sample application. It tests the application's <code>AlarmService</code> service.
8 <code>ServiceTestCase</code></a> test case class,
10 <code>TestCase</code></a> class. The test runner is
12 <code>InstrumentationTestRunner</code></a>.
16 how to create the <a href="AndroidManifest.html"><code>AndroidManifest.xml</code></a>
19 <code>AlarmServiceTest</code></a>, contains tests that demonstrate the following
24 Test setup: The <code>setUp()</code> method re-initializes the state of the
28 Service start: The <code>Service.testServiceCreate()</code> test confirms that the
34 The <a href="AndroidManifest.html">manifest</a> declares an <code>&lt;instrumentation&gt;</code>
36 element's <code>android:name</code> attribute specifies <code>InstrumentationTestRunner</code>
37 as the instrumentation to use. The <code>android:targetPackage</code> attribute specifies
38 <code>com.android.example.newalarm</code> as the name of the Android package that contains the
42 <strong>Note:</strong> <code>AlarmServiceTest.java</code> uses the Java package name
43 <code>com.example.android.newalarm</code>, which is the same package used by service under
44 test, <code>AlarmService.java</code>. This allows the test class to access members in the
46 the generated java file <code>R.java</code> for <code>AlarmServiceTest</code> uses the
47 Java package name <code>com.example.android.newalarm.test</code>. For the same reason, the
49 <code>com.example.android.newalarm.test</code>.