[webkit-dev] Test conversion to use W3C testharness.js
jacobg at adobe.com
Fri Mar 9 15:19:38 PST 2012
LayoutTests/resources is fine with me – that was the location I considered using originally and only moved them to LayoutTests/fast/js/resources because that is where js-test-pre and –post are.
I'll upload a new patch with the files in LayoutTests/resources.
From: Ryosuke Niwa <rniwa at webkit.org<mailto:rniwa at webkit.org>>
Date: Fri, 9 Mar 2012 14:37:18 -0800
To: Jacob Goldstein <jacobg at adobe.com<mailto:jacobg at adobe.com>>
Cc: "webkit-dev at lists.webkit.org<mailto:webkit-dev at lists.webkit.org>" <webkit-dev at lists.webkit.org<mailto:webkit-dev at lists.webkit.org>>
Subject: Re: [webkit-dev] Test conversion to use W3C testharness.js
On Fri, Mar 9, 2012 at 2:28 PM, Jacob Goldstein <jacobg at adobe.com<mailto:jacobg at adobe.com>> wrote:
Can we put them in LayoutTests/resources instead? I always find it hard to remember the path fast/js/resources.
I support the effort to make layout tests more compatible with W3C tests.
Is the plan to use testharness.js for all new tests? Or only tests that we intend to contribute back to W3C?
Another concern is that changes to testharness.js in the future that break backward compatibility could then break WebKit tests. This is an issue I plan to discuss with W3C members to determine if backward compatibility can be ensured.
There is no such a guarantee at the moment? That concerns me. On other hand, we wouldn't be importing ToT version of testharness.js so if such an incompatibility is introduced, we can migrate our tests on time as well.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev