Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

am a27afde3: Merge "Fix typo in activity_testing.jd" into lmp-mr1-dev

Browse Source 
automerge: 2eaf0b0

* commit '2eaf0b0a7b86304a739f91033e9f8f053123e74d':
  Fix typo in activity_testing.jd
This commit is contained in:
Yorke Lee
2014-10-31 18:45:18 +00:00
committed by android-build-merger
parent b2857d7e37 2eaf0b0a7b
commit 14deca6ded
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/html/tools/testing/activity_testing.jd
View File

@@ -242,7 +242,7 @@ parent.link=index.html
This changes when you run tests against the application. With instrumentation-based classes, This changes when you run tests against the application. With instrumentation-based classes,
you can invoke methods against the UI of the application under test. The other test classes you can invoke methods against the UI of the application under test. The other test classes
don't allow this. To run an entire test method on the UI thread, you can annotate the thread don't allow this. To run an entire test method on the UI thread, you can annotate the thread
with <code>@UIThreadTest</code>. Notice that this will run <em>all</em> of the method statements with <code>@UiThreadTest</code>. Notice that this will run <em>all</em> of the method statements
on the UI thread. Methods that do not interact with the UI are not allowed; for example, you on the UI thread. Methods that do not interact with the UI are not allowed; for example, you
can't invoke <code>Instrumentation.waitForIdleSync()</code>. can't invoke <code>Instrumentation.waitForIdleSync()</code>.
</p> </p>