Browser test for the push messaging feature

chrome/test/data/extensions/api_test/push_messaging/event_dispatch.js

Index: chrome/test/data/extensions/api_test/push_messaging/event_dispatch.js
diff --git a/chrome/test/data/extensions/api_test/push_messaging/event_dispatch.js b/chrome/test/data/extensions/api_test/push_messaging/event_dispatch.js
index 8c81771924217e458e6936b438f9069a485f7f3c..4784459a25503f8388260aabf79c4e2738273edd 100644
--- a/chrome/test/data/extensions/api_test/push_messaging/event_dispatch.js
+++ b/chrome/test/data/extensions/api_test/push_messaging/event_dispatch.js
@@ -3,6 +3,9 @@
 // found in the LICENSE file.
 
 function verifyDetails(details) {
+  // comment these back in for debugging

[Mihai Parparita -not on Chrome, 2012/09/13 20:37:09]

Please don't commit with commented-out code (especially because the code is
incorrect, the variable is called details, not message).

The assertEq calls will print the actual value if the comparison fails, so I
don't think you need the log statements in any case.

[Pete Williamson, 2012/09/14 19:14:48]

Done.

+  // console.log("push messaging payload is "    + message.payload);
+  // console.log("push messaging subChannel is " + message.subchannelId);
   chrome.test.assertEq(1, details.subchannelId);
   chrome.test.assertEq("payload", details.payload);
 }