Bug 59334 - [Qt] New tests introduced in r84742 fail
Summary: [Qt] New tests introduced in r84742 fail
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
Keywords: Qt, QtTriaged
Depends on:
Blocks: 59241 87008
  Show dependency treegraph
Reported: 2011-04-25 10:44 PDT by Csaba Osztrogonác
Modified: 2013-06-14 08:00 PDT (History)
7 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Csaba Osztrogonác 2011-04-25 10:44:26 PDT


Comment #14 From Alexey Proskuryakov 2011-04-23 20:21:44 PST (-) [reply]
Fixing Qt results seems to require some improvement of DRT result printing - not sure what the strategy is, but it seems that some Mac-specific messages are being already synthesized.
Comment 1 Csaba Osztrogonác 2011-04-25 10:48:14 PDT
Skipped by http://trac.webkit.org/changeset/84786
Comment 2 Robert Hogan 2011-06-09 12:53:34 PDT
(In reply to comment #0)
> http/tests/security/XFrameOptions/x-frame-options-deny.html
> http/tests/security/XFrameOptions/x-frame-options-parent-same-origin-deny.html

These two are benign, we have platform-specific results for the return codes in the same family of tests.

> http/tests/misc/will-send-request-returns-null-on-redirect.html

This one happens because the Qt API considers a load finished (and DRT dumps it results) when postProgressFinishedNotification() is fired from ProgressTracker::finalProgressComplete() for the main frame. By the time dispatchDidFailLoading() has been called for the iframe, the DRT has dumped.

I think other tests cope with this by putting a notifyDone() into the load event handler of any subframes. That is probably the fix here, or just accept Qt's platform specific results.

Alexey, does that sound sensible to you or do you suspect Qt is doing something wrong here?
Comment 3 Ádám Kallai 2013-02-14 02:39:28 PST
I'm reviewing qt test expectations. What do you think about this test? Should I update it or not? It seems this test result is correct with Wk2. 
Thanks for your help!

 * http/tests/misc/will-send-request-returns-null-on-redirect.html

--- /home/kadam/webkit/WebKit/WebKitBuild/Release/layout-test-results/http/tests/misc/will-send-request-returns-null-on-redirect-expected.txt
+++ /home/kadam/webkit/WebKit/WebKitBuild/Release/layout-test-results/http/tests/misc/will-send-request-returns-null-on-redirect-actual.txt
@@ -2,7 +2,6 @@
 <unknown> - didFinishLoading - willSendRequest <NSURLRequest URL http://www.example.com/, main document URL, http method GET> redirectResponse <NSURLResponse, http status code 302>
 Returning null for this redirect
- - didFailLoadingWithError: <NSError domain NSURLErrorDomain, code -999>
 This test checks to make sure that things behave as expected when the resource load delegate returns null in response to willSendRequest.