New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 677397 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

[CTS] CtsWebkitTestCases testClearFormData failed[cts ver: 7.0_r4]

Reported by zhongcq....@gmail.com, Dec 29 2016

Issue description

Steps to reproduce the problem:
1. run cts ,testClearFormData failed

What is the expected behavior?

What went wrong?
After we update Chrome to V55, then we can pass the CTS test.
In rom version: 54.0.2840.85 (fail)
PlayStore version: 55.0.2883.91 (pass)

Test Package :CtsWebkitTestCases
Main category : CtsWebkitTestCases
b.Firmware:7.0
c.CTS Ver:7.0_r4
d. Fail item as below:
Fail item	Fail details	Failure
Rate
android.webkit.cts.WebViewTest#testClearFormData	junit.framework.AssertionFailedError: unexpected timeout	1/1

e. Please refer to tool path and Single-run command as follows:
https://source.android.com/compatibility/cts/downloads.html
Single run command:
run cts -m CtsWebkitTestCases -t android.webkit.cts.WebViewTest#testClearFormData

Did this work before? N/A 

Chrome version: 54.0.2840.85  Channel: n/a
OS Version: N
Flash Version: 

From log:
12-24 20:04:53.482 19725 19741 I TestRunner: failed: testClearFormData(android.webkit.cts.WebViewTest)
12-24 20:04:53.482 19725 19741 I TestRunner: ----- begin exception -----
12-24 20:04:53.484 19725 19741 I TestRunner: junit.framework.AssertionFailedError: unexpected timeout
12-24 20:04:53.484 19725 19741 I TestRunner: at junit.framework.Assert.fail(Assert.java:50)
12-24 20:04:53.484 19725 19741 I TestRunner: at android.cts.util.PollingCheck.run(PollingCheck.java:60)
12-24 20:04:53.484 19725 19741 I TestRunner: at android.webkit.cts.WebViewTest.testClearFormData(WebViewTest.java:1200)

Get timeout when testClearFormData.This case test clear form data in website.

case code:
    public void testClearFormData() throws Throwable {
        if (!NullWebViewUtils.isWebViewAvailable()) {
            return;
        }
        try {
            startWebServer(false);
            WebSettings settings = mOnUiThread.getSettings();
            settings.setDatabaseEnabled(true);
            settings.setJavaScriptEnabled(true);
            WebViewDatabase webViewDatabase = WebViewDatabase.getInstance(getActivity());
            webViewDatabase.clearFormData();
            final String url = mWebServer.getAssetUrl(TestHtmlConstants.LOGIN_FORM_URL);
            mOnUiThread.loadUrlAndWaitForCompletion(url);
            new PollingCheck(TEST_TIMEOUT) {
                @Override
                public boolean check() {
                    return !WebViewDatabase.getInstance(getActivity()).hasFormData();
                }
            }.run();

            // Click submit (using JS, rather than simulated key presses, to avoid IME
            // inconsistencies).
            mOnUiThread.evaluateJavascript("document.getElementsByName('submit')[0].click()", null);
            new PollingCheck(TEST_TIMEOUT) {
                @Override
                public boolean check() {
                    return WebViewDatabase.getInstance(getActivity()).hasFormData();
                }
            }.run();
        } finally {
            WebViewDatabase.getInstance(getActivity()).clearFormData();
        }
    }

Earlier log exist socket closed.
12-24 20:04:53.305 19725 19776 W CtsTestServer: java.net.SocketException: Socket closed
12-24 20:04:53.305 19725 19776 W CtsTestServer: at java.net.PlainSocketImpl.socketAccept(Native Method)
12-24 20:04:53.305 19725 19776 W CtsTestServer: at java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:389)

We don't know why CtsTestServer throw SocketException.

why v54 fail,v55 pass?

thanks
 
cts_fail_logs.rar
5.8 MB Download
Cc: msrchandra@chromium.org
Labels: Needs-triage-Mobile Needs-Feedback Triaged-Mobile
@zhongcq.kai7 -- Thank You for the report.
Could you please upgrade to latest Chrome# 62.0.3202.84 and provide the latest behavior, if yes provide us with the screen cast which would help us in triaging the issue further.
Thanks in Advance. 
Status: WontFix (was: Unconfirmed)
Closing issue due to lack of feedback requested but not provided. If the issue still exists please open a new issue with the details requested.

Sign in to add a comment