Adding a test for measuring memory usage.

tools/perf/page_sets/top_25_usage.json

Index: tools/perf/page_sets/top_25_usage.json
diff --git a/tools/perf/page_sets/top_25_usage.json b/tools/perf/page_sets/top_25_usage.json
new file mode 100644
index 0000000000000000000000000000000000000000..6c0088a2438319bb42544eba64ea132ed0270751
--- /dev/null
+++ b/tools/perf/page_sets/top_25_usage.json
@@ -0,0 +1,31 @@
+{

[tonyg, 2012/11/02 18:57:34]

What do you have planned here? Can we add the interactions to the existing
top_25.json page set rather than creating a new one?

[marja, 2012/11/05 14:43:25]

If I do that, I also need to recreate the .wpr file, and then the scrolling
benchmark results before and after the .wpr page recreation won't be comparable.
I added a different file to keep the scrolling benchmark unaffected by my
changes. And this would happen every time I add more tests to this file.

-> I can merge this with the top_25.json if you say it's ok to affect the
scrolling benchmark.

I suggest I add top_25_usage.json (and leave top_25.json and the scrolling
benchmark intact), and when we're done with adding the memory tests, I migrate
the scroll benchmark to use it too. Then we'll have only one discontinuity point
for the scrolling benchmark. Wdyt?

+    "description": "Pages for executing tests which not only load the pages, but also do some user actions.",
+    "credentials_path": "../data/credentials.json",
+    "archive_path": "../data/top_25_usage.wpr",
+    "pages": [
+        {
+            "name": "Facebook",
+            "url": "http://www.facebook.com/barackobama",
+            "why": "top social,Public profile",
+            "credentials": "facebook",
+            "scroll_is_infinite": true,
+            "interactions": [
+                {
+                    "type": "TestHelper",
+                    "code": "window.__ClickLinkWithText(\"Women for Obama\");",
+		    "completion": "window.__ReadyStateComplete()"

[tonyg, 2012/11/02 18:57:34]

How many interactions do you have planned? If it's only a handful, I really like
this factoring better:
"interactions": [
  {
    "type": "ClickLink",
    "link_text": "Women for Obama"
  }
]

Then click_link_interaction.py is responsible for running just the JS it needs
and waiting for ready state completion.

[marja, 2012/11/05 14:43:25]

Done. In the latest version, I'm just passing the json to the javascript side,
and there deciding which function to call, and reading the needed params.

[marja, 2012/11/05 15:14:48]

Oops, I forgot to add that I don't have a clear vision about how many
interactions we'll have. At least link clicking and scrolling.

I tried to do this without having to dispatch "ClickLink" to "get click_link.js
and execute a function on it", so now all interactions would be in the same
file... but this is probably not the right thing.

I'll try to figure out something more robust.

[marja, 2012/11/05 15:26:44]

I updated the interaction CL. Now I dispatch "clickLink" to "load
interaction_clickLink.js and call clickLink(json) on it". This causes minor file
naming pain, but if we can take it, then the system is more robust (no need to
add dispatching rules to the python side).

+                },
+                {
+                    "type": "TestHelper",
+                    "code": "window.__ClickLinkWithText(\"About\");",
+		    "completion": "window.__ReadyStateComplete()"
+                },
+                {
+                    "type": "TestHelper",
+                    "code": "window.__ClickLinkWithText(\"Home\");",
+		    "completion": "window.__ReadyStateComplete()"
+                }
+            ]
+        }
+    ]
+}