Don't test for AppCache callbacks.
Remove the code in WebSettingsTest#testAppCacheEnabled which asserts
that AppCachee callbacks actually happen; the implementation of AppCache
in Chromium is going to be removed in future so it won't be possible for
this test to pass beyond that point.
Bug: 156266477
Test: atest WebSettingsTest#testAppCacheEnabled
Merged-In: Iff215f060387eb5cfd798caa56dcd02ea1e9d7af
Change-Id: Iff215f060387eb5cfd798caa56dcd02ea1e9d7af
diff --git a/tests/tests/webkit/src/android/webkit/cts/WebSettingsTest.java b/tests/tests/webkit/src/android/webkit/cts/WebSettingsTest.java
index d004565..ecfd2ec 100644
--- a/tests/tests/webkit/src/android/webkit/cts/WebSettingsTest.java
+++ b/tests/tests/webkit/src/android/webkit/cts/WebSettingsTest.java
@@ -739,17 +739,10 @@
Thread.sleep(1000);
assertEquals("Loaded", mOnUiThread.getTitle());
- // Test that when AppCache is enabled and a valid path is provided, we
- // get an AppCache callback of some kind.
- mSettings.setAppCachePath(getActivity().getDir("appcache", 0).getPath());
- mOnUiThread.loadUrlAndWaitForCompletion(url);
- new PollingCheck(WEBVIEW_TIMEOUT) {
- @Override
- protected boolean check() {
- return mOnUiThread.getTitle() != null
- && mOnUiThread.getTitle().endsWith("Callback");
- }
- }.run();
+ // We used to test that when AppCache is enabled and a valid path is
+ // provided, we got an AppCache callback of some kind, but AppCache is
+ // deprecated on the web and will be removed from Chromium in the
+ // future, so this test has been removed.
}
// Ideally, we need a test case for the enabled case. However, it seems that