On Mon, 2011-07-11 at 13:09 +1000, Ian Booth wrote: > NB I have found that FF5 fails when running some of the tests. They > work > fine in Chromium and python-htmlbrowser used by the test runner. I > have > not yet tracked down the cause. The failing tests are from the > (former) > lazr-js suite.
I fixed a few unit tests that Jenkins reported as failing last month
just after I landed html5browser
* Some tests assumed all browsers were broken, webkit was not,
gecko was. Tests should not assume all engines are broken; they
must be written to pass both browsers.
* Some tests assumed that invalid HTML could be used in the test,
but webkit and IE correct the markup to build a consistent DOM.
Write valid markup; no not assume all browsers will interpret
markup the same way.
* Tests left cruft behind in the DOM. Browsers may interpret these
differently. I believe one test was broken when two branch were
merged about the same time into devel; each passed in it's
branch, but not together.
--
__Curtis C. Hovey_________
http://launchpad.net/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
