wine users - Dec 2009 - Application robust testing

Hello all, 

Right now I have a windows application in the testing phase, my boss also want
me to test it on the wine platform, it basiclly works. but He also ask me to do
a random user input testing generated by software. i have been trying to use x11
extension xtest to do it. it works some how, but I for the edit control i can
not get focused on. so i am thinking writing a testing program in wine.

Can I modify the wine source code to create another process at the same time
wine is loading the application exe, the new process will share the same
resource with the application, and it can use send_message/get message to
simulate user input? will there be other options to write a automatically
testing process?

Thanks, 
Alex

siliconcreature wrote:
>
>Hello all, 
>
>Right now I have a windows application in the testing phase, my boss also
want me to test it on the wine platform, it basically
>works. but he also asked me to do a random user input testing generated by
software. i have been trying to use x11 extension xtest
>to do it. it works some how, but I for the edit control i can not get
focused on. so i am thinking writing a testing program in
>wine. 
>
Automated testing is not something that is simple to create.  This can be a
lengthy process.
>
>Can I modify the wine source code to create another process at the same time
wine is loading the application exe, the new process
>will share the same resource with the application, and it can use
send_message/get message to simulate user input? will there be
>other options to write a automatically testing process?
>
Might I suggest that you look at the tests that Wine runs within the distributed
code for ideas on how to write an automated program test?  The tests send
messages to the active window to simulate user button presses, menu selections
and other inputs.  You can test the output against what you expect.  However, I
don't think this includes graphical capabilities, but you could ask on the
wine-development mailing list for additional suggestions.

James McKenzie

thanks, 
I am reading the code in the directory dlls/user32/test/, and winedebug=message
option, but their code is testing the application created in the code, not some
other application already running in the other process. wine-development
mailing-list is not focusing on this kind of issue. the technique in windows is
using dll injection, but in wine, it is kind of not necessary, since we had the
source code already.