Hi Austin,<br><br>Not sure if you are aware of it but there is also cxtest which was written by codeweavers under the gpl. See <a href="http://cxtest.ifne.eu:82/">http://cxtest.ifne.eu:82/</a> it seems they (still?) use it regulary to track regressions. I haven't looked at it and don't know that autohotkey stuff but how do both differ? Wouldn't it be better to continue with cxtest? Or perhaps it would be better to use autohotkey (assuming it is a widely used app) and extend it so that cxtest can be dropped.<br>
<br>Roderick<br><br><div class="gmail_quote">On Wed, Mar 25, 2009 at 12:33 AM, Austin English <span dir="ltr"><<a href="mailto:austinenglish@gmail.com">austinenglish@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Howdy,<br>
<br>
I'm planning on applying for Google Summer of Code 2009. I'm pretty<br>
sure most people reading this list already know me, but for those that<br>
don't, I frequently triage bugs in Bugzilla, help users on the forum,<br>
and a few other things. I've also done quite a bit of work testing<br>
wine on more obscure OS's (OpenSolaris, FreeBSD, OS X, �NetBSD,<br>
OpenBSD).<br>
<br>
I'd like to implement an application test suite. It's something that's<br>
been discussed for Wine for quite a while, but has never been put into<br>
place. I took a bit of time a while back and hacked couple a couple<br>
quick scripts as a test, and got a script to automatically install<br>
Firefox 3 in Wine using AutoHotKey (<a href="http://www.autohotkey.com/" target="_blank">http://www.autohotkey.com/</a>). I've<br>
made a couple more scripts as well, but they don't match Windows<br>
behavior because of bug (<a href="http://bugs.winehq.org/show_bug.cgi?id=10147" target="_blank">http://bugs.winehq.org/show_bug.cgi?id=10147</a>)<br>
hint, hint (disclaimer, I haven't tested that script in a while, been<br>
busy with exams, so that bug might be fixed...I don't think it has<br>
though).<br>
<br>
My plan to implement it is to make a script, that can be used<br>
standalone, in conjunction with Patchwatcher, or any other script, to<br>
test wine against several real world applications. I make a very quick<br>
proof of concept (attached), which is based off of winetricks. It's<br>
_REALLY_ rough at the moment, (I haven't had time to mess with it<br>
lately), but demonstrates the idea. The script setups a clean<br>
WINEPREFIX, installs autohotkey, removes the Z: symlink for braindead<br>
installers that search the entire hard drive, and sets up a link to<br>
it's install cache (essentially winetrickscache). From there, it makes<br>
a copy of this prefix, so on subsequent installers/applications, we<br>
can restore the clean prefix and save a few seconds.<br>
<br>