Add simple pepper plugin telemetry test

tools/perf/benchmarks/scheduler.py

 # Copyright 2014 The Chromium Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 from telemetry import test
 from measurements import smoothness
 
 
 @test.Disabled('linux')  # crbug.com/368767
 class SchedulerToughSchedulingCases(test.Test):
   """Measures rendering statistics while interacting with pages that have
   challenging scheduling properties.
 
   https://docs.google.com/a/chromium.org/document/d/
       17yhE5Po9By0sCdM1yZT3LiUECaUr_94rQt9j-4tOQIM/view"""
   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() ?