Sync Cache API tests w/ web-platform-tests

third_party/WebKit/LayoutTests/http/tests/cachestorage/serviceworker/cache-add-expected.txt

Index: third_party/WebKit/LayoutTests/http/tests/cachestorage/serviceworker/cache-add-expected.txt
diff --git a/third_party/WebKit/LayoutTests/http/tests/cachestorage/serviceworker/cache-add-expected.txt b/third_party/WebKit/LayoutTests/http/tests/cachestorage/serviceworker/cache-add-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..7f55b7c64162095dc3c86c1ea04475590060e317
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/http/tests/cachestorage/serviceworker/cache-add-expected.txt
@@ -0,0 +1,20 @@
+This is a testharness.js-based test.
+PASS Cache.add and Cache.addAll 
+PASS Cache.add called with no arguments 
+PASS Cache.add called with relative URL specified as a string 
+PASS Cache.add called with non-HTTP/HTTPS URL 
+PASS Cache.add called with Request object 
+PASS Cache.add called with POST request 
+PASS Cache.add called twice with the same Request object 
+PASS Cache.add called with Request object with a used body 
+PASS Cache.add with request that results in a status of 404 
+PASS Cache.add with request that results in a status of 500 
+PASS Cache.addAll with no arguments 
+PASS Cache.addAll with a mix of valid and undefined arguments 
+PASS Cache.addAll with an empty array 
+PASS Cache.addAll with string URL arguments 
+PASS Cache.addAll with Request arguments 
+PASS Cache.addAll with a mix of succeeding and failing requests 
+FAIL Cache.addAll called with the same Request object specified twice promise_test: Unhandled rejection with value: "assert_promise_rejects: Cache.addAll should throw InvalidStateError if the same request is added twice. Promise did not reject."

[jsbell, 2015/12/01 20:50:49]

Test assumes that the body will be consumed. This looks wrong upstream if I'm
reading the fetch spec correctly, since request's empty body won't be disturbed.

[yhirano, 2015/12/02 06:58:52]

A request with a null body should not be disturbed, but a request with an empty
body should be disturbed.

[jkarlin, 2015/12/02 16:42:45]

Agreed. So should we incorporate the change and file a bug upstream? 

[jsbell, 2015/12/02 17:17:46]

+1, but I want to hear if yhirano agrees.

[yhirano, 2015/12/03 01:58:18]

Oh, sorry, I misunderstood.
You're right, request's body is always null (not empty) because its method is
'GET', and hence the reuqest cannot be locked or disturbed.

+Harness: the test ran to completion.
+