From d0646dca40ff740bd49755ad60751678b0ccca52 Mon Sep 17 00:00:00 2001 From: Mark Doliner Date: Wed, 27 Aug 2014 16:04:02 -0700 Subject: Small documentation fixes across many files. Change-Id: I3e8787ce4bc6018ea1dc9aef2a2cd4e0a8dde663 --- docs/html/tools/testing/testing_eclipse.jd | 2 +- docs/html/tools/testing/testing_otheride.jd | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/html/tools/testing') 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.

Another useful convention is to add the method testPreconditions() 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.

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

Another useful convention is to add the method testPreConditions() 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.

-- cgit v1.1