[webkit-dev] Switching to new-run-webkit-tests

Dirk Pranke dpranke at chromium.org
Wed Jul 6 13:32:48 PDT 2011

On Wed, Jul 6, 2011 at 9:04 AM, Xan Lopez <xan at gnome.org> wrote:
> On Wed, Jul 6, 2011 at 5:58 PM, Adam Roben <aroben at apple.com> wrote:
>> On Jul 6, 2011, at 11:53 AM, Adam Roben wrote:
>>> Now that more and more ports are switching to NRWT, it would be great for someone to explain what the best practices are for dealing with failing and flaky tests.
>> Two specific questions I have:
>> 1) Are the ports that have switched to NRWT no longer using Skipped files?
>> 2) Are the ports that have switched to NRWT now using test_expectations.txt files?
> GTK+ still uses Skipped. NWRT understands both (although you cannot
> have both at the same time), but of course test_expectations.txt
> allows much more flexibility.
>> But I'm interested in a more general overview, too.
> Same here. FWIW, the Chrome test_expectations.txt file has a lengthy
> introductory comment with some guidelines.

I was meaning to stuff all that on a web page and remove it from the
chrome test_expectations.txt file (since it's awfully wordy to
duplicate in each expectations file, and I think slightly out of date
to boot). I'll try to draft up something shortly this afternoon.

-- Dirk

More information about the webkit-dev mailing list