<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;">On Jul 13, 2014, at 11:39 AM, Alexander Almaleh <<a href="mailto:sashoalm@gmail.com">sashoalm@gmail.com</a>> wrote:<br><div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">While testing the Polygon() function for my bug report - <a href="https://bugs.winehq.org/show_bug.cgi?id=36891">https://bugs.winehq.org/show_bug.cgi?id=36891</a>, I used a test program that performs a Polygon() operation on a memory device context, and then saves it to a bitmap - i.e. a *.bmp file.<div>
<br></div><div>I then compared the bitmaps produced under Windows and Wine using a program I wrote in Qt, that just compares width/height, and then makes a pixel-by-pixel comparison (and the Polygon() function did indeed produce a slightly different bitmap).</div>
<div><br></div><div>Since this process can be easily automated, I'm wondering if such a framework is already being used? If not, I could probably make a sample test program and image comparison tool, if anyone is interested.</div>
<div><br></div><div>It would be fairly easily to spot all kinds of bugs in the drawing functions using such a testing system.</div></div></blockquote><br></div><div>There are such tests. They were central to the development of the DIB engine. See dlls/gdi32/tests/dib.c.</div><div><br></div><div>The tests run under Wine or on Windows, not both in concert. They can't directly take output from one and compare to the other. Also, one doesn't want to store a slew of bitmaps into the tests for pixel-wise comparison. So, the approach is to take a hash of the bitmap data and compare to a hash of a known-good bitmap.</div><br><div>-Ken</div><div><br></div></body></html>