[Telemetry] Convert long running user stories to the System Health format.

tools/perf/benchmarks/battor.py

Index: tools/perf/benchmarks/battor.py
diff --git a/tools/perf/benchmarks/battor.py b/tools/perf/benchmarks/battor.py
index 1cfaf8da98d9e448290d2add060b869cc8897393..2eef41f32009b76401293007b3a840202f132988 100644
--- a/tools/perf/benchmarks/battor.py
+++ b/tools/perf/benchmarks/battor.py
@@ -130,3 +130,34 @@ class BattOrTrivialPages(_BattOrBenchmark):
   @classmethod
   def Name(cls):
     return 'battor.trivial_pages'
+

[petrcermak, 2016/08/25 09:57:19]

nit: there should be 2 blank lines between top-level definitions.

[rnephew (Reviews Here), 2016/08/25 15:28:57]

Charlies CL at https://codereview.chromium.org/2239053003/ will cause this new
pageset to run with battor tests, so I will be deleting these benchmarks.

+class DesktopBattOrLongRunning(_BattOrBenchmark):

[rnephew (Reviews Here), 2016/08/24 17:50:45]

If my understanding of how the system_health.memory_* tests work is correct, the
new pages should automatically be picked up by it correct?

If that is the case I can get rid of these battor tests (or keep them, depending
on popular consensus). I just wanted to make sure at least once benchmark is
running the new pages.

[petrcermak, 2016/08/25 09:57:18]

All benchmarks that don't specify |case| or have case='long_running' will
automatically pick these up. As far as I can tell, BattOr benchmarks have
case='load'
(https://cs.chromium.org/chromium/src/tools/perf/benchmarks/battor.py?l=63), so
will NOT pick up your stories. Rather than define another benchmark, I suggest
you either:

1) Change battor benchmarks to use ALL SH stories (not just the loading ones) by
removing "case='load'".
2) Modify the SystemHealthStorySet constructor to accept a |cases| list of
strings (instead of just a |case| string) and change the BattOr benchmark ot
pass cases=['load', 'long_running'].

[petrcermak, 2016/08/25 09:57:18]

If for some reason you decide to spin up a separate benchmark, then please pull
all the common code (all three methods, CreateStorySet,
ShouldTearDownStateAfterEachStoryRun, Name) into an abstract superclass.

+  PLATFORM = 'desktop'
+
+  def CreateStorySet(self, options):
+    return page_sets.SystemHealthStorySet(platform=self.PLATFORM,
+                                          case='long_running')
+
+  @classmethod
+  def ShouldTearDownStateAfterEachStoryRun(cls):
+    return True
+
+  @classmethod
+  def Name(cls):
+    return 'battor.long_running_%s' % cls.PLATFORM
+
+
+class MobileBattOrLongRunning(_BattOrBenchmark):
+  PLATFORM = 'mobile'
+
+  def CreateStorySet(self, options):
+    return page_sets.SystemHealthStorySet(platform=self.PLATFORM,
+                                          case='long_running')
+
+  @classmethod
+  def ShouldTearDownStateAfterEachStoryRun(cls):
+    return True
+
+  @classmethod
+  def Name(cls):
+    return 'battor.long_running_%s' % cls.PLATFORM