[webkit-dev] WPT tests and runtime-enabled features
foolip at chromium.org
Wed Jun 7 06:12:10 PDT 2017
FWIW, in Chromium, if we had an off-by-default feature that we wanted to
test using wpt, we would probably use the
On Sat, Jun 3, 2017 at 1:03 AM, youenn fablet <youennf at gmail.com> wrote:
> Hi Ali,
> Yes this is something we should have a solution for. Right now, we have
> two ways:
> - Enabling the runtime-enabled flag only in DumpRenderTree/
> - Updating WebKit testharnessreport.js to call internal APIs for some/all
> WPT tests
> Ideally, we should be able to set additional configuration information to
> WPT tests without modifying them.
> A configuration file alongside the WPT test might be feasible and could
> supersede the <!--- webkit-test-runner [enableFeatureName=true] -->
> Folder-based hierarchical configuration might be nice but I am unsure
> whether that would meet the complexity tradeoff bar.
> Nothing yet started there so any help would be greatly appreciated!
> Le ven. 2 juin 2017 à 13:37, Ali Juma <ajuma at chromium.org> a écrit :
>> Hi all,
>> While a feature is in development behind a runtime-enabled flag, is there
>> a way to write tests in web-platform-tests that enable the feature when
>> they're run as part of LayoutTests? Adding "<!--- webkit-test-runner
>> [enableFeatureName=true] -->" tags would technically work but seems a bit
>> The point of this would be to be able to use web platform tests as
>> regression tests while developing a feature, allowing the tests to be
>> upstreamed sooner and saving having to write them outside of
>> web-platform-tests first and then move them over later.
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev