<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; ">
<div><br>
</div>
<div><br>
</div>
<span id="OLK_SRC_BODY_SECTION">
<div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<span style="font-weight:bold">From: </span>ext Benjamin Poulain <<a href="mailto:benjamin@webkit.org">benjamin@webkit.org</a>><br>
<span style="font-weight:bold">Date: </span>Saturday, February 9, 2013 12:52 AM<br>
<span style="font-weight:bold">To: </span>Noam Rosenthal <<a href="mailto:noam.rosenthal@nokia.com">noam.rosenthal@nokia.com</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:rniwa@webkit.org">rniwa@webkit.org</a>" <<a href="mailto:rniwa@webkit.org">rniwa@webkit.org</a>>, "<a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a>" <<a href="mailto:webkit-dev@lists.webkit.org">webkit-dev@lists.webkit.org</a>><br>
<span style="font-weight:bold">Subject: </span>Re: [webkit-dev] Testing feature suggestion: animation/interaction pixel-results "on the fly"<br>
</div>
<div><br>
</div>
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>On Fri, Feb 8, 2013 at 3:16 PM, <span dir="ltr"><<a href="mailto:noam.rosenthal@nokia.com" target="_blank">noam.rosenthal@nokia.com</a>></span> wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
<div>The problem with dynamic features of the web like animations/interactions is that they're non-deterministic, or at least a lot less deterministic than static features of the web like layouts.</div>
<div>Ref tests, pixel tests etc. are tools built for deterministic testing: load a file, take a snapshot, compare against a result. Testing an animation (or a filter) needs to feel a lot more dynamic and expressive: Animate green boxes, make sure that they're
within a particular range at particular points in time".</div>
</div>
</blockquote>
<div><br>
</div>
<div>
<div>The tests also have to be deterministic and comprehensive. I am afraid of loosing both with the Render-to-Canvas approach.</div>
</div>
</div>
</div>
</blockquote>
</span><span id="OLK_SRC_BODY_SECTION">
<blockquote id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style="BORDER-LEFT: #b5c4df 5 solid; PADDING:0 0 0 5; MARGIN:0 0 0 5;">
<div>
<div class="gmail_quote">
<div>
<div><br>
</div>
<div>Can you give concrete examples of the kind of bugs you are hunting, and why testing cannot use the two methods suggested?</div>
</div>
</div>
</div>
</blockquote>
</span>
<div>I did not say they cannot be tested with the two methods suggested :) It's more about a preference to move some of those decisions from the test infrastructure to the test itself, but potentially those bugs could be tested in either way.</div>
<div>Examples for bugs I've encountered/reviewed and can use better in-motion testing (note that those are specific to Qt/EFL, but I'm sure there are tons of bugs like this that come up for Apple/Google as well)</div>
<div><a href="http://trac.webkit.org/changeset/140825">http://trac.webkit.org/changeset/140825</a></div>
<div><a href="http://trac.webkit.org/changeset/142112">http://trac.webkit.org/changeset/142112</a></div>
<div><a href="http://trac.webkit.org/changeset/134953">http://trac.webkit.org/changeset/134953</a></div>
<div><a href="https://bugs.webkit.org/show_bug.cgi?id=109179">https://bugs.webkit.org/show_bug.cgi?id=109179</a></div>
<div><br>
</div>
<div>Controlling the clock and programmatically sampling the end result would definitely make those more testable, but of course any progress in this area would be beneficial and my preference to a canvas-based API is more of an opinion.</div>
<div><br>
</div>
</body>
</html>