Bug 62888
| Summary: | [Qt] DOM2 XHTML tests with WebKit2: 15 tests skip even though not in skip list. | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Venkat Penukonda <venkatpenukonda> |
| Component: | WebKit Qt | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED INVALID | ||
| Severity: | Normal | CC: | laszlo.gombos, marcelo.lira, venkatpenukonda |
| Priority: | P2 | Keywords: | LayoutTestFailure, Qt |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Linux | ||
Venkat Penukonda
LayoutTests/dom/xhtml/level2/html/
5 of the tests in this path are listed in qt-wk2 Skip list. But when run, 15 tests get skipped and a total of 668 tests are run.
Expected Result: Only the tests in the skip list should be skipped (meaning 678 tests to be run).
I tried this test on following configuration:
Platform: Ubuntu Linux desktop,
Qt: 4.7.x
WebKit: Trunk rev. 89027
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Laszlo Gombos
Can you please list the failing test cases ?
Note that QtWebKit at the moment has no plans to support java, so the following cases are not relevant for QtWebKit:
- dom/xhtml/level2/html/HTMLAppletElement*.xhtml
Venkat Penukonda
Retested the LayoutTests/dom/xhtml/level2/html tests on webkit trunk rev. 89839.
with default run, 673 tests ran and all succeeded.
This includes the one HTMLApplet test:
dom/xhtml/level2/html/HTMLAppletElement11.xhtml
with --skip=ignore run, 683 tests run and all succeeded.
This means 10 tests are in skip list, but they do pass when run.
These 10 should be:
dom/xhtml/level2/html/HTMLAppletElement01.xhtml
to
dom/xhtml/level2/html/HTMLAppletElement10.xhtml
I will try to run these 10 tests on CI system and update this bug with my findings.
Marcelo Lira
In my ubuntu machine wk1 and wk2 runs the same number of tests.
Jocelyn Turcotte
=== 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.