Made ChromeSyncShellTest.apk run on the fyi-tests bot.

build/android/buildbot/bb_device_steps.py

 #!/usr/bin/env python
 # Copyright (c) 2013 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.
 
 import collections
 import glob
 import hashlib
 import json
 import os
@@ skipping 49 matching lines @@
       'ContentShell.apk',
       'org.chromium.content_shell_apk',
       'ContentShellTest',
       'content:content/test/data/android/device_files'),
     I('ChromeShell',
       'ChromeShell.apk',
       'org.chromium.chrome.shell',
       'ChromeShellTest',
       'chrome:chrome/test/data/android/device_files',
       constants.CHROME_SHELL_HOST_DRIVEN_DIR),
+    I('ChromeSyncShell',

[jbudorick, 2014/08/26 17:59:53]

Mentioned offline, but for the record: This will run ChromeSyncShellTests
wherever we run the other instrumentation tests on bots still running the
buildbot scripts. While this is what we eventually want to do, it isn't how we
want to start.

Add a separate test step command that just runs these sync tests and have the
fyi bots run that step.

+      'ChromeSyncShell.apk',
+      'org.chromium.chrome.browser.sync',
+      'ChromeSyncShellTest.apk',
+      'chrome:chrome/test/data/android/device_files'),
     I('AndroidWebView',
       'AndroidWebView.apk',
       'org.chromium.android_webview.shell',
       'AndroidWebViewTest',
       'webview:android_webview/test/data/device_files'),
     ])
 
 VALID_TESTS = set(['chromedriver', 'chrome_proxy', 'gpu', 'mojo',
                    'telemetry_perf_unittests', 'ui', 'unit', 'webkit',
                    'webkit_layout', 'webrtc_chromium', 'webrtc_native'])
@@ skipping 654 matching lines @@
 
   if options.coverage_bucket:
     setattr(options, 'coverage_dir',
             os.path.join(CHROME_OUT_DIR, options.target, 'coverage'))
 
   MainTestWrapper(options)
 
 
 if __name__ == '__main__':
   sys.exit(main(sys.argv))