Use the ReloadBypassingCache policy

Source/web/tests/WebFrameTest.cpp

Index: Source/web/tests/WebFrameTest.cpp
diff --git a/Source/web/tests/WebFrameTest.cpp b/Source/web/tests/WebFrameTest.cpp
index 890bb5b1ca09794147879f80db02198e4e1c44e2..201f760154b7aece56fc489aa54ce92b2aabb493 100644
--- a/Source/web/tests/WebFrameTest.cpp
+++ b/Source/web/tests/WebFrameTest.cpp
@@ -5449,4 +5449,14 @@ TEST_F(WebFrameTest, NotifyManifestChange)
     EXPECT_EQ(14, webFrameClient.manifestChangeCount());
 }
 
+TEST_F(WebFrameTest, ReloadIgnoringCache)

[ppi, 2014/06/04 16:23:59]

This asserts on the resulting policy being "ReloadBypassingCache" - should the
test be called ReloadBypassingCache?

What is it that will cause the resulting policy be ReloadBypassingCache? Could
you indicate that in a comment?

[clamy, 2014/06/04 16:39:25]

This test checks that asking a reload on a frame with the option ignoringCache
set to true results in the policy being ReloadBypassingCache. I think the name
is right for the test, and added a comment.

[ppi, 2014/06/04 19:25:39]

ReloadIgnoringCacheData is a name of caching policy that results in cache
revalidation, not bypassing, right? I think we might want to call this
"bypassing" whenever possible, even if existing helper functions don't.

[clamy, 2014/06/04 20:14:20]

Done.

+{
+    registerMockedHttpURLLoad("foo.html");
+    FrameTestHelpers::WebViewHelper webViewHelper;
+    webViewHelper.initializeAndLoad(m_baseURL + "foo.html", true);
+    WebFrame* frame = webViewHelper.webView()->mainFrame();
+    FrameTestHelpers::reloadFrameIgnoringCache(frame);
+    EXPECT_EQ(WebURLRequest::ReloadBypassingCache, frame->dataSource()->request().cachePolicy());
+}
+
 } // namespace