[webkit-dev] WebKit unit test framework
Adam Barth
abarth at webkit.org
Wed Apr 20 13:20:06 PDT 2011
Looks like folks don't have a strong opinion about this topic. I'd
recommend just picking something that works and giving it a try. I
suspect many different frameworks would all work fine.
Adam
On Mon, Apr 18, 2011 at 11:48 AM, Dirk Pranke <dpranke at chromium.org> wrote:
> I'd add "maintained" to your list, but otherwise it looks pretty good :)
>
> It would also be nice if the testing framework supported parallel or
> distributed execution, but not many do.
>
> -- Dirk
>
> On Mon, Apr 18, 2011 at 11:36 AM, David Levin <levin at chromium.org> wrote:
>> Issue: There has been a long standing bug to add unit tests to WebKit
>> (https://bugs.webkit.org/show_bug.cgi?id=21010). It was also mentioned on
>> webkit-dev that it would be helpful in various cases.
>> Landscape: Surveying WebKit, it is looks like there are at least three
>> testing frameworks being used: TestWebKitAPI/WebKitAPITest (in Tools),
>> QTest, gtest (in Source/WebKit/chromium/). However, only one TestWebKitAPI
>> has been used so far (as far as I can tell) for testing core WebKit items
>> like WTF (though I was unaware of TestWebKitAPI until Friday).
>> It seems like a good way to think about the issue of which to use in general
>> in WebKit would be to decide on what would be desired in our framework and
>> then see how each matches up.
>> Here's my take on this. (It may be biased toward what I am familiar with but
>> I welcome others to add their own criteria.)
>> Criteria
>> Musts:
>>
>> Compatible license with WebKit
>> Builds/Can be built on the many platforms and build systems supported by
>> WebKit (ideally without extra installs).
>>
>> Useful:
>>
>> Easy to write tests
>> Hackable to suit our needs
>> Well tested features (to support hackability/stability)
>> Supports filtering of tests so you can run just the test you care about (and
>> easily listing the tests).
>> Supports writing out values when there is test failure. (For example, if the
>> is verifying that A == B but that is not true, then the values of A and B
>> should be printed.)
>> Well documented
>>
>> thanks,
>> dave
>>
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>>
>>
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
More information about the webkit-dev
mailing list