First unit test for Google Now extension

chrome/chrome_tests_unit.gypi

Index: chrome/chrome_tests_unit.gypi
diff --git a/chrome/chrome_tests_unit.gypi b/chrome/chrome_tests_unit.gypi
index 6c2983a3a98ce923131a4228edc7eab83b54eeb2..d257224d92a6001688e3b21c1b3598f21d0a979a 100644
--- a/chrome/chrome_tests_unit.gypi
+++ b/chrome/chrome_tests_unit.gypi
@@ -1069,6 +1069,9 @@
         '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',