[webkit-dev] Top 100 sites browsing tests proprosal

[Ryosuke Niwa]

See my posts about archive.org-based performance tests. We can use the same
infrastructure to make sure WebKit doesn't crash :)

In fact... running top 100 websites as performance tests might just do the
trick because we'll catch any crashes (can't catch assertion failures
though :( ).

On Sat, Jan 21, 2012 at 2:12 AM, Sergio Villar Senin <svillar at igalia.com>wrote:

> Hi,
>
> I've been thinking about this for some time now, but only a recent bug
> I'm constantly hitting these days
> (https://bugs.webkit.org/show_bug.cgi?id=76574) triggered this email
> [1]. What I would like to propose here is to have a battery of tests
> that would check that the most visited sites (let's say the top 100 for
> example) are correctly loaded by WebKit. By correctly loaded, I don't
> mean layout or ref tests, they'll just check that the page poad ends
> without any assertion.
>
> I know that trunk is for raw development but having >25k layout tests
> passing is nothing if a so popular site as Wikipedia triggers an
> assertion while being loaded. The obvious answer is "ok so we need more
> tests", we all agree on that, but having like "real-word" permanent
> tests would not harm I guess (and probably help defining more layout
> tests).
>
> I haven't took a detailed look at them, but maybe these main sites
> browsing tests could be part of the perf tests rniwa and others recently
> setup.
>
> What do you think?
>
> BR
>
> [1] note that I am not blaming anyone in particular, we all add bugs,
> just that this one finally flipped the switch :)
> _______________________________________________
> webkit-dev mailing list
> webkit-dev at lists.webkit.org
> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-dev/attachments/20120426/f5b288a0/attachment.html>