Add simple pepper plugin telemetry test

tools/perf/benchmarks/scheduler.py

Index: tools/perf/benchmarks/scheduler.py
diff --git a/tools/perf/benchmarks/scheduler.py b/tools/perf/benchmarks/scheduler.py
index a6fb1a64f1449663e487e60eda7360399eb69558..dddafd78571eccf7e49f83062aa69d83b93ed621 100644
--- a/tools/perf/benchmarks/scheduler.py
+++ b/tools/perf/benchmarks/scheduler.py
@@ -16,3 +16,13 @@ class SchedulerToughSchedulingCases(test.Test):
   test = smoothness.Smoothness
   page_set = 'page_sets/tough_scheduling_cases.py'
 
+@test.Disabled('android')  # pepper plugin is not supported on android
+class SchedulerToughPepperCases(test.Test):
+  """Measures rendering statistics while interacting with pages that have
+  pepper plugins"""
+  test = smoothness.Smoothness
+  page_set = 'page_sets/tough_pepper_cases.py'

[nednguyen, 2014/06/06 01:56:37]

This should be tough_pepper_cases.ToughPepperCases with Dave's change in
https://codereview.chromium.org/311193003/

+
+  def CustomizeBrowserOptions(self, options):
+    # This is needed for testing pepper plugin.
+    options.AppendExtraBrowserArgs('--enable-pepper-testing')

[nednguyen, 2014/06/06 01:56:37]

This will be enough for the bot since it will pick up your pepper plugin change,
however this may fail on local machine which doesn't have the TOT chromium
build. 

@Nat, Tony: do we care about the second case? If so, I suggest you implement the
CanRunOnBrowser for your tough_pepper_cases page set. 

[Yufeng Shen (Slow to review), 2014/06/06 16:15:19]

@Tony: this new page_set meant for measuring the mean_input_event_latency of a
simple pepper plugin. mean_input_event_latency is available only when the
chromium
build has my recent change. But the test itself will still run on old chrome
build, only that this specific metric won't be reported. Do we still need
CanRunOnBrowser() to guard against running this benchmark on old chrome build ?
If we really need to, can we use chrome revision checking in CanRunOnBrowser() ?