Processing groups with nextPollSeconds === undefined

chrome/browser/resources/google_now/background_unittest.gtestjs

Index: chrome/browser/resources/google_now/background_unittest.gtestjs
diff --git a/chrome/browser/resources/google_now/background_unittest.gtestjs b/chrome/browser/resources/google_now/background_unittest.gtestjs
index ff8fdcb79987943b008aa69738812ad856a2c5a6..e179d075e7ce37a1048d0c9dff0afa2e8ccae68a 100644
--- a/chrome/browser/resources/google_now/background_unittest.gtestjs
+++ b/chrome/browser/resources/google_now/background_unittest.gtestjs
@@ -381,8 +381,6 @@ TEST_F(
       // the new group from the server.
 
       // Setup and expectations.
-      Date.now = function() { return 500; };
-
       var serverResponse = {
         groups: {
           GROUP1: {},
@@ -407,8 +405,7 @@ TEST_F(
 
       var expectedUpdatedGroups = {
         GROUP1: {
-          cards: [],
-          nextPollTime: Date.now()

[robliao, 2013/10/23 17:15:29]

Is this not critical to the test? Seems like nextPollTime is always set.

[vadimt, 2013/10/23 17:19:28]

I started developing tests for parseAndShowNotificationCards, created a first
one, and switched to something else. There will be more tests for it, and
they'll test everything. This test concentrates on the logic of adding/removing
groups.

+          cards: []
         },
         GROUP2: {
           cards: ['c2'],