add ScreenSaverUnlock autotest and teach ScreenSaverRunning to log in

client/site_tests/desktopui_ScreenSaverUnlock/control

Index: client/site_tests/desktopui_ScreenSaverUnlock/control
diff --git a/client/site_tests/desktopui_ScreenSaverRunning/control b/client/site_tests/desktopui_ScreenSaverUnlock/control
similarity index 53%
rename from client/site_tests/desktopui_ScreenSaverRunning/control
rename to client/site_tests/desktopui_ScreenSaverUnlock/control
index af5b1f56739d83602eb4945ea79f8aef4fddd21f..56e9fed63a23a46e6271076d004751a33eba75cd 100644
--- a/client/site_tests/desktopui_ScreenSaverRunning/control
+++ b/client/site_tests/desktopui_ScreenSaverUnlock/control
@@ -1,16 +1,16 @@
-# Copyright (c) 2009 The Chromium OS Authors. All rights reserved.
+# Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 AUTHOR = "Chrome OS Team"
-NAME = "ScreenSaverRunning"
+NAME = "ScreenSaverUnlock"
 TIME = "SHORT"
 TEST_CATEGORY = "Functional"
 TEST_CLASS = "desktopui"
 TEST_TYPE = "client"
 
 DOC = """
-This test checks if the screen saver process is alive and running
+This test checks if the screen saver can be unlocked
 """
 
-job.run_test('desktopui_ScreenSaverRunning')
+job.run_test('desktopui_ScreenSaverUnlock')