From 54dee349976eaafe7df3a2bb48e9fce2b964a7f0 Mon Sep 17 00:00:00 2001 From: Quddus Chong Date: Fri, 3 Apr 2015 17:06:28 -0700 Subject: docs: Fixed broken urls in the UI testing training main page and revised intro to the 'Testing UI for a Single App' class. Change-Id: I0e2a49b639101a7607e8e90cf830d9d449ad6328 --- docs/html/training/testing/ui-testing/espresso-testing.jd | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/html/training/testing/ui-testing/espresso-testing.jd') diff --git a/docs/html/training/testing/ui-testing/espresso-testing.jd b/docs/html/training/testing/ui-testing/espresso-testing.jd index e5e37f7..85f4ba4 100644 --- a/docs/html/training/testing/ui-testing/espresso-testing.jd +++ b/docs/html/training/testing/ui-testing/espresso-testing.jd @@ -60,8 +60,8 @@ trainingnavtop=true

- UI tests that involve user interactions - within a single app help to ensure that users do not + Testing user interactions + within a single app helps to ensure that users do not encounter unexpected results or have a poor experience when interacting with your app. You should get into the habit of creating user interface (UI) tests if you need to verify that the UI of your app is functioning correctly. -- cgit v1.1