On Sat, May 23, 2009 at 2:35 AM, fcmartins <wineforum-user@xxxxxxxxxx> wrote: > > fcmartins wrote: >> >> I went to check back your post and I'm wondering what you mean actually by "test >> graphical applications": can you give a brief idea on how this is done, ie, how to test graphical output? > > > Ok, replying to myself, you'll be using autohotkey which allows > > "Automate game actions by detecting images and pixel colors" > > Is this the case? I don't plan on testing games. Too much possibility for error. I rather plan on testing more basic/functional applications, e.g.,: Shell script: rm -rf ~/.wine wineboot wine Autohotkey.exe test1.ahk test1.ahk: Ifdoesnotexist foo.exe, download foo.exe sha1sum foo.exe run foo.exe winwait, Foo program, , 10 if errorlevel, "error, program doesn't work" "program launched fine". exit rm -rf ~/.wine wine autohotkey.exe test2.ahk ... then analyzing the logs for "test failed", "todo_fixed", etc. It's a lot of work, but should help greatly. Keep in mind this is related to, but different from what you're proposing. The vast majority of bugs can't be automatically tested for (or would take a lot of work to test). It's much easier to manually test for those things. Wine is a volunteer open source project. If you want to contribute, but can't program, help test bugs. Developer time is much better spent fixing bugs and writing patches than testing for old bugs that may already be fixed. -- -Austin
