[Telemetry] Replace RunStressMemorey with RunPageInteraction

tools/perf/page_sets/top_25.py

Index: tools/perf/page_sets/top_25.py
diff --git a/tools/perf/page_sets/top_25.py b/tools/perf/page_sets/top_25.py
index 212292e97faf27fdbddde8f249c9682424d140d7..44458c6e7388ffad05447a02d7252af21302fc13 100644
--- a/tools/perf/page_sets/top_25.py
+++ b/tools/perf/page_sets/top_25.py
@@ -45,7 +45,7 @@ class GoogleWebSearchPage(Top25Page):
     action_runner.NavigateToPage(self)
     action_runner.WaitForElement(text='Next')
 
-  def RunStressMemory(self, action_runner):
+  def RunPageInteractions(self, action_runner):

[tonyg, 2014/10/06 21:06:36]

This was a nice, general purpose page set. But now we're closely coupling it to
the memory measurement's script. Is there another way we can preserve the
generality of page sets like this?

[nednguyen, 2014/10/06 21:40:40]

The coupling already exists with these RunStressMemory function that can be run
if we use memory measurement. 

To me, the real bug that causes the coupling is that we have the mindset "write
a user story A for measurement Y", whereas the better model should be: user
stories describe what user actually do in the real world, and we take various
measurements around each of them.

Even though the URLs are the same, the user stories in this page set are
actually different for memory vs smoothness. This movement will only reduce the
coupling, make the page set *more* general since it allows other measurement to
run user stories with actions which once were only issued in 'RunStressMemory".

[nduca, 2014/10/07 17:46:48]

backin gup... maybe the thing to think of here is that a user story has a single
run method... you call run on it and it runs the story. start to finish.

so, a user story set is a list of many stories. some scroll. some just navigate.
some just open and close gmail.

pagesets are just sets of user stories about web pages.


right now we have "one page can has many stories in it" --- thats the core thing
I think we want to do away with. Rather, if you want the same URL to be
scrollable and be able to open/close discard, then make it have two user
stories.


some measurements make no sense on some kinds of stories. e.g. there's no point
in calculating memory levels on smoothness. so, then you need a mechanism to
tell if a story is useful to a measurement. i think that's whats being lost in
this refactoring --- ned, how does memory measurement's canRunForPage know that
a page stresses memory?

     interaction = action_runner.BeginGestureInteraction(
         'ScrollAction', is_smooth=True)
     action_runner.ScrollPage()
@@ -121,7 +121,7 @@ class GmailPage(Top25Page):
         'window.gmonkey !== undefined &&'
         'document.getElementById("gb") !== null')
 
-  def RunStressMemory(self, action_runner):
+  def RunPageInteractions(self, action_runner):
     old_href = _GetCurrentLocation(action_runner)
     action_runner.ClickElement(
         'a[href="https://mail.google.com/mail/u/0/?shva=1#starred"]')
@@ -169,7 +169,7 @@ class GoogleCalendarPage(Top25Page):
         })();''')
     action_runner.Wait(1)
 
-  def RunStressMemory(self, action_runner):
+  def RunPageInteractions(self, action_runner):
     action_runner.ClickElement('div[class~="navForward"]')
     action_runner.Wait(2)
     action_runner.WaitForElement('div[class~="navForward"]')
@@ -255,7 +255,7 @@ class GooglePlusPage(Top25Page):
     action_runner.NavigateToPage(self)
     action_runner.WaitForElement(text='Home')
 
-  def RunStressMemory(self, action_runner):
+  def RunPageInteractions(self, action_runner):
     action_runner.ClickElement(text='Home')
     action_runner.Wait(2)
     action_runner.WaitForElement(text='Profile')
@@ -310,7 +310,7 @@ class BlogspotPage(Top25Page):
     action_runner.NavigateToPage(self)
     action_runner.WaitForElement(text='accessibility')
 
-  def RunStressMemory(self, action_runner):
+  def RunPageInteractions(self, action_runner):
     action_runner.ClickElement(text='accessibility')
     action_runner.WaitForNavigate()
     interaction = action_runner.BeginGestureInteraction(
@@ -350,7 +350,7 @@ class WordpressPage(Top25Page):
         # pylint: disable=C0301
         'a[href="http://en.blog.wordpress.com/2012/08/30/new-themes-able-and-sight/"]')
 
-  def RunStressMemory(self, action_runner):
+  def RunPageInteractions(self, action_runner):
     interaction = action_runner.BeginGestureInteraction(
         'ScrollAction', is_smooth=True)
     action_runner.ScrollPage()
@@ -392,7 +392,7 @@ class FacebookPage(Top25Page):
     action_runner.NavigateToPage(self)
     action_runner.WaitForElement(text='About')
 
-  def RunStressMemory(self, action_runner):
+  def RunPageInteractions(self, action_runner):
     action_runner.ClickElement(text='About')
     action_runner.WaitForNavigate()
     action_runner.ClickElement(text='The Audacity of Hope')