summaryrefslogtreecommitdiffstats
path: root/docs/html/tools/testing
diff options
context:
space:
mode:
authorMark Doliner <mark@kingant.net>2014-08-27 16:04:02 -0700
committerMark Doliner <mark@kingant.net>2014-09-05 13:57:51 -0700
commitd0646dca40ff740bd49755ad60751678b0ccca52 (patch)
tree8e1cf2b4efebac703e253a1f14abc34557e8154e /docs/html/tools/testing
parent2d3571cc17a5a6b1072951227d889ce14a3f88cf (diff)
downloadframeworks_base-d0646dca40ff740bd49755ad60751678b0ccca52.zip
frameworks_base-d0646dca40ff740bd49755ad60751678b0ccca52.tar.gz
frameworks_base-d0646dca40ff740bd49755ad60751678b0ccca52.tar.bz2
Small documentation fixes across many files.
Change-Id: I3e8787ce4bc6018ea1dc9aef2a2cd4e0a8dde663
Diffstat (limited to 'docs/html/tools/testing')
-rw-r--r--docs/html/tools/testing/testing_eclipse.jd2
-rw-r--r--docs/html/tools/testing/testing_otheride.jd2
2 files changed, 2 insertions, 2 deletions
diff --git a/docs/html/tools/testing/testing_eclipse.jd b/docs/html/tools/testing/testing_eclipse.jd
index 7d3be47..6c9d55b 100644
--- a/docs/html/tools/testing/testing_eclipse.jd
+++ b/docs/html/tools/testing/testing_eclipse.jd
@@ -218,7 +218,7 @@ from Eclipse</a>.
<p>
Another useful convention is to add the method <code>testPreconditions()</code> to your test
class. Use this method to test that the application under test is initialized correctly. If this
- test fails, you know that that the initial conditions were in error. When this happens, further
+ test fails, you know that the initial conditions were in error. When this happens, further
test results are suspect, regardless of whether or not the tests succeeded.
</p>
<p>
diff --git a/docs/html/tools/testing/testing_otheride.jd b/docs/html/tools/testing/testing_otheride.jd
index 9484158..a774087 100644
--- a/docs/html/tools/testing/testing_otheride.jd
+++ b/docs/html/tools/testing/testing_otheride.jd
@@ -281,7 +281,7 @@ $ android create test-project -m ../HelloAndroid -n HelloAndroidTest -p HelloAnd
<p>
Another useful convention is to add the method <code>testPreConditions()</code> to your test
class. Use this method to test that the application under test is initialized correctly. If this
- test fails, you know that that the initial conditions were in error. When this happens, further
+ test fails, you know that the initial conditions were in error. When this happens, further
test results are suspect, regardless of whether or not the tests succeeded.
</p>
<p>