Implement the window verifier in the Automated Installer Testing Framework.

chrome/test/mini_installer/config/chrome_installed.prop

Index: chrome/test/mini_installer/config/chrome_installed.prop
diff --git a/chrome/test/mini_installer/config/chrome_installed.prop b/chrome/test/mini_installer/config/chrome_installed.prop
index 9db2a192c9a7275e0665c8057c019cb791ac5d84..9a752a506db98ace0f229b7b500cc8b5deceef0e 100644
--- a/chrome/test/mini_installer/config/chrome_installed.prop
+++ b/chrome/test/mini_installer/config/chrome_installed.prop
@@ -2,5 +2,8 @@
   "RegistryEntries": {
     "HKEY_CURRENT_USER\\Software\\Google\\Update\\Clients\\{8A69D345-D564-463c-AFF1-A69D9E530F96}":
         {"exists": true}
+  },
+  "Windows": {
+    "Welcome to Chrome": {"exists": true}

[gab, 2013/08/13 17:49:27]

The installer launches chrome.exe and exits shortly after without waiting for it
to actually launch.

Asserting that the window is up immediately after the install completes will
result in a flaky test as it relies on chrome.exe having been scheduled by the
OS on the machine and having made it far enough to have a window with the right
title before this verifier kicks in.

Instead I think we should add --do-not-launch-chrome to the install command
being tested.

Then add another command which runs chrome.exe and then verifies another state
made of chrome_installed.prop + chrome_running.prop.

The command that runs chrome.exe should also be made so that it only returns
when the window is up (essentially using the verifier you wrote to probe for the
Chrome window in a loop before returning).

   }
 }