First unit test for Google Now extension

chrome/chrome_tests_unit.gypi

 # Copyright 2012 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.
 {
   'targets': [
     {
       # This target contains mocks and test utilities that don't belong in
       # production libraries but are used by more than one test executable.
       'target_name': 'test_support_common',
       'type': 'static_library',
@@ skipping 1051 matching lines @@
         'browser/profiles/gaia_info_update_service_unittest.cc',
         'browser/profiles/off_the_record_profile_impl_unittest.cc',
         'browser/profiles/profile_downloader_unittest.cc',
         'browser/profiles/profile_info_cache_unittest.cc',
         'browser/profiles/profile_info_cache_unittest.h',
         'browser/profiles/profile_info_util_unittest.cc',
         'browser/profiles/profile_manager_unittest.cc',
         'browser/profiles/profile_shortcut_manager_unittest_win.cc',
         'browser/renderer_host/plugin_info_message_filter_unittest.cc',
         'browser/renderer_host/web_cache_manager_unittest.cc',
+        'browser/resources/google_now/background.js',
+        'browser/resources/google_now/unit_test/background.gtestjs',

[arv (Not doing code reviews), 2013/06/18 17:47:10]

No other tests uses a unit_test dir. How about 

'browser/resources/google_now/background_unittest.gtestjs',

[vadimt, 2013/06/18 23:12:25]

Here, we have choice between uniformity (and benefits of this uniformity are not
so obvious, while it's messy to keep everything in one directory) and clarity
(with a separate directory for tests). In my eyes, the benefits of clarity
overweight.
But if you insist, I'll put everything in one folder.

[arv (Not doing code reviews), 2013/06/19 13:31:01]

All other chrome tests go next to the file they are testing.

+        'browser/resources/google_now/unit_test/background_globals.js',

[arv (Not doing code reviews), 2013/06/19 13:31:01]

background_test_util.js maybe?

[vadimt, 2013/06/19 18:10:47]

All done.

         'browser/resources/print_preview/data/measurement_system.js',
         'browser/resources/print_preview/data/measurement_system_unittest.gtestjs',
         'browser/resources/print_preview/print_preview_utils.js',
         'browser/resources/print_preview/print_preview_utils_unittest.gtestjs',
         'browser/resources_util_unittest.cc',
         'browser/rlz/rlz_unittest.cc',
         'browser/safe_browsing/browser_feature_extractor_unittest.cc',
         'browser/safe_browsing/chunk_range_unittest.cc',
         'browser/safe_browsing/client_side_detection_host_unittest.cc',
         'browser/safe_browsing/client_side_detection_service_unittest.cc',
@@ skipping 1486 matching lines @@
               # more details.
               'DebugInformationFormat': '3',
               'ProgramDataBaseFileName': '<(PRODUCT_DIR)/unit_tests.exe.pdb',
             },
           },
         },
       ],
     }],
   ],  # 'conditions'
 }