From 3df06ddd33a6c51813171951fd82b34f7039144d Mon Sep 17 00:00:00 2001 From: Yorke Lee Date: Tue, 28 Oct 2014 15:16:52 -0700 Subject: [PATCH] Fix typo in activity_testing.jd UIThreadTest -> UiThreadTest Change-Id: I32e8303b13c6631f12c974d464ec16f9dfca7071 --- docs/html/tools/testing/activity_testing.jd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/html/tools/testing/activity_testing.jd b/docs/html/tools/testing/activity_testing.jd index 88ac9b2351f7f..8baa35de88e8e 100644 --- a/docs/html/tools/testing/activity_testing.jd +++ b/docs/html/tools/testing/activity_testing.jd @@ -242,7 +242,7 @@ parent.link=index.html 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 don't allow this. To run an entire test method on the UI thread, you can annotate the thread - with @UIThreadTest. Notice that this will run all of the method statements + with @UiThreadTest. Notice that this will run all of the method statements on the UI thread. Methods that do not interact with the UI are not allowed; for example, you can't invoke Instrumentation.waitForIdleSync().