Implement InstanceID API functions.

chrome/test/data/extensions/api_test/instance_id/delete_token/delete_token.js

Index: chrome/test/data/extensions/api_test/instance_id/delete_token/delete_token.js
diff --git a/chrome/test/data/extensions/api_test/instance_id/delete_token/delete_token.js b/chrome/test/data/extensions/api_test/instance_id/delete_token/delete_token.js
new file mode 100644
index 0000000000000000000000000000000000000000..f1147f9c461ec308b92b332d56d0052bd1ce3cb8
--- /dev/null
+++ b/chrome/test/data/extensions/api_test/instance_id/delete_token/delete_token.js
@@ -0,0 +1,94 @@
+// Copyright 2015 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.
+
+function deleteTokenWithoutParameters() {
+  try {
+    chrome.instanceID.deleteToken();
+    chrome.test.fail(
+        "Calling deleteToken without parameters should fail.");
+  } catch (e) {
+    chrome.test.succeed();
+  };
+}
+
+function deleteTokenWithoutCallback() {
+  try {
+    chrome.instanceID.deleteToken({"authorizedEntity": "1", "scope": "GCM"});
+    chrome.test.fail(
+        "Calling deleteToken without callback should fail.");
+  } catch (e) {
+    chrome.test.succeed();
+  };
+}
+
+function deleteTokenWithoutAuthorizedEntity() {
+  try {
+    chrome.instanceID.deleteToken({"scope": "GCM"});

[fgorski, 2015/05/07 19:59:53]

applies elsewhere: add callback here, as you don't know why this thing failed
otherwise.

also, it seems to me that things your are testing for here are enforced by IDL
and you could skip these tests.

[jianli, 2015/05/07 20:47:01]

Good catch. Added.
I think it is probably better to do our own validation in case that we might
change to use other definition.

+    chrome.test.fail(
+        "Calling deleteToken without authorizedEntity parameter should fail.");
+  } catch (e) {
+    chrome.test.succeed();
+  };
+}
+
+function deleteTokenWithInvalidAuthorizedEntity() {
+  try {
+    chrome.instanceID.deleteToken({"authorizedEntity": 1, "scope": "GCM"});
+    chrome.test.fail(
+        "Calling deleteToken with invalid authorizedEntity parameter " +
+        "should fail.");
+  } catch (e) {
+    chrome.test.succeed();
+  };
+}
+
+function deleteTokenWithoutScope() {
+  try {
+    chrome.instanceID.deleteToken({"authorizedEntity": "1"});
+    chrome.test.fail(
+        "Calling deleteToken without scope parameter should fail.");
+  } catch (e) {
+    chrome.test.succeed();
+  };
+}
+
+function deleteTokenWithInvalidScope() {
+  try {
+    chrome.instanceID.deleteToken({"authorizedEntity": "1", "scope": 1});
+    chrome.test.fail(
+        "Calling deleteToken with invalid scope parameter should fail.");
+  } catch (e) {
+    chrome.test.succeed();
+  };
+}
+
+function deleteToken() {
+  chrome.instanceID.deleteToken(

[fgorski, 2015/05/07 19:59:53]

shouldn't you get the token first here?

[jianli, 2015/05/07 20:47:01]

This is to test calling deleteToken without getToken.

+    {"authorizedEntity": "1", "scope": "GCM"},
+    function(token) {
+      if (chrome.runtime.lastError) {
+        chrome.test.fail(
+            "chrome.runtime.lastError: " + chrome.runtime.lastError.message);
+        return;
+      }
+      if (!token) {
+        chrome.test.fail("Empty token returned.");
+        return;
+      }
+
+      chrome.test.succeed();
+    }
+  );
+}
+
+chrome.test.runTests([
+  deleteTokenWithoutParameters,
+  deleteTokenWithoutCallback,
+  deleteTokenWithoutAuthorizedEntity,
+  deleteTokenWithInvalidAuthorizedEntity,
+  deleteTokenWithoutScope,
+  deleteTokenWithInvalidScope,
+  // TODO(jianli): To be enabled when deleteToken is implemented.
+  //deleteToken,

[fgorski, 2015/05/07 19:59:53]

test the following: getToken->Delete->getToken

[jianli, 2015/05/07 20:47:01]

Done.

+]);