Initial commit for the Automated Installer Testing Framework.

chrome/test/mini_installer_test/data/chrome_installed.prop

Index: chrome/test/mini_installer_test/data/chrome_installed.prop
diff --git a/chrome/test/mini_installer_test/data/chrome_installed.prop b/chrome/test/mini_installer_test/data/chrome_installed.prop
new file mode 100644
index 0000000000000000000000000000000000000000..0946fe9ce6da3d49bd6b405a262a4b66b71664d9
--- /dev/null
+++ b/chrome/test/mini_installer_test/data/chrome_installed.prop
@@ -0,0 +1,5 @@
+{

[gab, 2013/07/31 13:45:16]

As suggested earlier, how about putting these in a config/ directory rather than
data/?

This is more inline with what these files actually are imo..

[sukolsak, 2013/07/31 18:20:30]

Done.

+  "RegistryEntries": {
+    "HKEY_CURRENT_USER\\Software\\Google\\Update\\Clients\\{8A69D345-D564-463c-AFF1-A69D9E530F96}": {"expected": true}

[gab, 2013/07/30 20:44:14]

Wrap {"expected": true} to the next line, 4 extra spaces in, to try to respect
the 80 columns rule as best as possible (I don't think breaking down the key's
path itself is necessary).

Same comment for all other such json files.

[grt (UTC plus 2), 2013/07/31 17:20:05]

Strictly speaking, the presence/absence of the registry value named "pv" within
the Clients key is the thing that indicates to Google Update that a product is
installed. I think the framework should make the same test.

Ultimately, the framework should verify that the version number present in the
"pv" registry value is the one that was expected given the install/update
operation that preceded the verification.

Please at least put a TODO somewhere that this should be fixed down the road.

[gab, 2013/07/31 17:46:19]

Eventually the goal is to have ALL the registry values listed here; so I think
it's ok for now to leave it as an implied TODO that this list will grow (since
we can't put comments in JSON anyways...).

[sukolsak, 2013/07/31 18:20:30]

Done.

+  }
+}