smoothness.scrolling_tough_ad_cases to use browser driven scrolls

tools/perf/page_sets/repeatable_synthesize_scroll_gesture_shared_state.py

Index: tools/perf/page_sets/repeatable_synthesize_scroll_gesture_shared_state.py
diff --git a/tools/perf/page_sets/fling_gesture_supported_shared_state.py b/tools/perf/page_sets/repeatable_synthesize_scroll_gesture_shared_state.py
similarity index 53%
copy from tools/perf/page_sets/fling_gesture_supported_shared_state.py
copy to tools/perf/page_sets/repeatable_synthesize_scroll_gesture_shared_state.py
index afcdcde542b85aca4529aa526fabc242648bf2f3..2c7f97394f17577c4bbd7cc09dcb52a15de4626f 100644
--- a/tools/perf/page_sets/fling_gesture_supported_shared_state.py
+++ b/tools/perf/page_sets/repeatable_synthesize_scroll_gesture_shared_state.py
@@ -6,11 +6,12 @@ import logging
 from telemetry.page import shared_page_state
 
 
-class FlingGestureSupportedSharedState(
-    shared_page_state.Shared10InchTabletPageState):
+class RepeatableSynthesizeScrollGestureSharedState(

[Sami, 2015/08/18 15:06:46]

nit: should this be "synthetic" or "synthesized" instead of "synthesize"?

[alex clarke (OOO till 29th), 2015/08/19 11:42:20]

I can reorder  Repeatable and Synthesize

[Sami, 2015/08/19 17:21:19]

I meant that "synthesize scroll gesture" sounds a bit weird. Since we already
have synthetic scroll gestures in telemetry, how about calling this
browser_side_scroll_gesture to distinguish it?

+    shared_page_state.SharedPageState):
 
   def CanRunOnBrowser(self, browser_info, _):
-    if not browser_info.HasFlingGestureSupport():
-      logging.warning('Browser does not support fling gestures, skipping test')
+    if not browser_info.HasRepeatableSynthesizeScrollGesture():
+      logging.warning('Browser does not support repatable scroll gestures, '
+                      'skipping test')
       return False
     return True