For those of you looking into flaky tests -
I've found a surprising number of tests that are flaky because they use a
setTimeout to guarantee that a resource (usually an iframe) has loaded.
This leads to slower running, flaky tests. To address this, change the
tests upstream to use onload instead and make the world a better place :)
I'm converting all of the editing tests now.
Julie
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
