Performance tests for bookmark sync.

chrome/chrome_tests.gypi

 # Copyright (c) 2011 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.
 
 {
   'variables' : {
     'pyautolib_sources': [
       'app/chrome_command_ids.h',
       'app/chrome_dll_resource.h',
       'common/automation_constants.h',
@@ skipping 3354 matching lines @@
         'test/live_sync/live_sessions_sync_test.cc',
         'test/live_sync/live_sessions_sync_test.h',
         'test/live_sync/live_themes_sync_test.cc',
         'test/live_sync/live_themes_sync_test.h',
         'test/live_sync/live_typed_urls_sync_test.cc',
         'test/live_sync/live_typed_urls_sync_test.h',
         'test/live_sync/live_sync_extension_helper.cc',
         'test/live_sync/live_sync_extension_helper.h',
         'test/live_sync/live_sync_test.cc',
         'test/live_sync/live_sync_test.h',
+        'test/live_sync/live_sync_timing_helper.cc',
+        'test/live_sync/live_sync_timing_helper.h',
         'test/live_sync/many_client_live_bookmarks_sync_test.cc',
         'test/live_sync/many_client_live_passwords_sync_test.cc',
         'test/live_sync/many_client_live_preferences_sync_test.cc',
         'test/live_sync/migration_errors_test.cc',
         'test/live_sync/multiple_client_live_bookmarks_sync_test.cc',
         'test/live_sync/multiple_client_live_passwords_sync_test.cc',
         'test/live_sync/multiple_client_live_preferences_sync_test.cc',
         'test/live_sync/multiple_client_live_sessions_sync_test.cc',
         'test/live_sync/multiple_client_live_typed_urls_sync_test.cc',
+        'test/live_sync/performance_live_bookmarks_sync_test.cc',

[Raghu Simha, 2011/06/16 22:42:55]

I just realised that adding these tests to the sync_integration_tests target
will cause them to be run on the buildbots and trybots for every patch. I don't
think we want to do this. Perhaps we should create a new target called
sync_performance_tests. Let me get back to you on where they should live.

[braffert, 2011/06/17 18:19:46]

I discussed this with Anna a while ago, and we decided that the goal would be to
leave the add/update/delete cases for each datatype as part of the integration
tests.  The time taken for these test cases to finish is slightly longer, but
still comparable to the rest of the integration tests.  Only the benchmark takes
a significant amount of time, so it should eventually be moved somewhere else.

         'test/live_sync/single_client_live_apps_sync_test.cc',
         'test/live_sync/single_client_live_bookmarks_sync_test.cc',
         'test/live_sync/single_client_live_extensions_sync_test.cc',
         'test/live_sync/single_client_live_passwords_sync_test.cc',
         'test/live_sync/single_client_live_preferences_sync_test.cc',
         'test/live_sync/single_client_live_sessions_sync_test.cc',
         'test/live_sync/single_client_live_themes_sync_test.cc',
         'test/live_sync/single_client_live_typed_urls_sync_test.cc',
         'test/live_sync/two_client_live_apps_sync_test.cc',
         'test/live_sync/two_client_live_autofill_sync_test.cc',
@@ skipping 733 matching lines @@
       ]
     }],  # 'coverage!=0'
   ],  # 'conditions'
 }
 
 # Local Variables:
 # tab-width:2
 # indent-tabs-mode:nil
 # End:
 # vim: set expandtab tabstop=2 shiftwidth=2: