From e4c1e7db167fb1372bd16422fdcb05b2343abf06 Mon Sep 17 00:00:00 2001 From: Pin Ting Date: Thu, 5 Jan 2012 15:52:10 +0800 Subject: [PATCH] Fixes typo. Change-Id: I79e09594017d1e2decb927bff0d7c8a0fc2873f2 --- docs/html/guide/topics/testing/testing_android.jd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/html/guide/topics/testing/testing_android.jd b/docs/html/guide/topics/testing/testing_android.jd index c8a3f6e7af55..adbc59d7cea1 100755 --- a/docs/html/guide/topics/testing/testing_android.jd +++ b/docs/html/guide/topics/testing/testing_android.jd @@ -318,7 +318,7 @@ parent.link=index.html A useful general test case class, especially if you are just starting out with Android testing, is {@link android.test.AndroidTestCase}. It extends both {@link junit.framework.TestCase} and {@link junit.framework.Assert}. It provides the - JUnit-standard setUp() and tearDown() methods, as well as well as + JUnit-standard setUp() and tearDown() methods, as well as all of JUnit's Assert methods. In addition, it provides methods for testing permissions, and a method that guards against memory leaks by clearing out certain class references.

@@ -401,7 +401,7 @@ parent.link=index.html Mock objects isolate tests from a running system by stubbing out or overriding normal operations. For example, a {@link android.test.mock.MockContentResolver} replaces the normal resolver framework with its own local framework, which is isolated - from the rest of the system. MockContentResolver also also stubs out the + from the rest of the system. MockContentResolver also stubs out the {@link android.content.ContentResolver#notifyChange(Uri, ContentObserver, boolean)} method so that observer objects outside the test environment are not accidentally triggered.

-- 2.11.0