PyAuto tests derived from PolicyTestBase now clear the profile.

chrome/test/pyautolib/pyauto.py

Index: chrome/test/pyautolib/pyauto.py
diff --git a/chrome/test/pyautolib/pyauto.py b/chrome/test/pyautolib/pyauto.py
index 959ca457e330ad9991f26edce9d3108f41e37e78..2ce6fbdf28cadcabde2b5041e0ef6a2d0b577749 100755
--- a/chrome/test/pyautolib/pyauto.py
+++ b/chrome/test/pyautolib/pyauto.py
@@ -3678,7 +3678,7 @@ class PyUITest(pyautolib.PyUITestBase, unittest.TestCase):
         lambda: self.ApplyAccelerator(IDC_EXIT)), \
         'Session manager did not restart after logout.'
 
-    self.setUp()
+    PyUITest.setUp(self)

[Nirnimesh, 2012/03/03 01:24:15]

why?

[frankf, 2012/03/03 01:54:13]

I don't want Logout() to call the derived class's setUp(). PolicyTestBase's
setUp() setups a test server and logs you back in. I haven't fully tested this
CL yet, so assumption may be wrong in other scenarios (e.g. chromeos_login)

On 2012/03/03 01:24:15, Nirnimesh wrote:

[dtu, 2012/03/03 02:14:41]

The intent in Logout() and Signout() is to do only the ChromeOS-specific testing
channel setup, not the test-specific setup from when a test overrides setUp(). I
would prefer if the ChromeOS-specific stuff is pulled out to its own method to
make this distinction clearer, but this is okay too.

[Nirnimesh, 2012/03/03 02:22:01]

Makes sense.

[frankf, 2012/03/03 03:48:05]

Agree. Now we have setUp(), SetUp(), __SetUp()
:)

On 2012/03/03 02:14:41, Dave Tu wrote:

 
   def LockScreen(self):
     """Locks the screen on chromeos.
@@ -3726,7 +3726,7 @@ class PyUITest(pyautolib.PyUITestBase, unittest.TestCase):
     assert self.WaitForSessionManagerRestart(
         lambda: self._GetResultFromJSONRequest(cmd_dict, windex=None)), \
         'Session manager did not restart after logout.'
-    self.setUp()
+    PyUITest.setUp(self)
 
   def GetBatteryInfo(self):
     """Get details about battery state.