Bug 99034 - [Qt][WK2] some cookie related tests fail after unskipped in r131044
Summary: [Qt][WK2] some cookie related tests fail after unskipped in r131044
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: Tools / Tests (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 87008 103890
  Show dependency treegraph
 
Reported: 2012-10-11 05:54 PDT by Kristóf Kosztyó
Modified: 2014-02-03 03:22 PST (History)
7 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kristóf Kosztyó 2012-10-11 05:54:58 PDT
These tests fail after they unskipped in r131044 <http://trac.webkit.org/changeset/131044>

http/tests/cookies/third-party-cookie-relaxing.html
http/tests/security/cookies/third-party-cookie-blocking-user-action.html
http/tests/security/cookies/third-party-cookie-blocking-xslt.xml
http/tests/security/cookies/third-party-cookie-blocking.html
Comment 1 Kristóf Kosztyó 2012-10-11 06:04:31 PDT
I skipped them to paint the bots green in r131049: <http://trac.webkit.org/changeset/131049>
Comment 2 Jussi Kukkonen (jku) 2012-10-12 00:26:25 PDT
Thanks, and sorry for making your bots red. From memory, these tests deal with the safari third party cookie policy which isn't implemented by others.

Just so I could learn something from this: Does the Qt EWS not run tests? Is there a way to know which ones do run tests and which don't?
Comment 3 Csaba Osztrogonác 2012-10-12 00:29:13 PDT
As far as I know only the Mac and the Chromium EWS bots run tests.
Comment 4 Allan Sandfeld Jensen 2012-12-03 07:44:11 PST
The TestRunner API used here is not implemented in WebKitTestrunner, so it is a not strictly a Qt problem but a WK2 one.
Comment 5 Jocelyn Turcotte 2014-02-03 03:22:54 PST
=== Bulk closing of Qt bugs ===

If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary.

If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.