[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wine-devel
Subject:    Cross-Library tests, tests using multiple processes
From:       Stefan =?iso-8859-1?q?D=F6singer?= <stefandoesinger () gmx ! at>
Date:       2007-03-30 17:26:21
Message-ID: 200703301926.24329.stefandoesinger () gmx ! at
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Hi,
Screen resolution setting in DirectX games is still a huge mess. I want to fix 
it properly finally. Write tests to find out what really happens in windows, 
then implement it.

Unfortunately that fails at the tests already. Our test framework is mainly 
limited to test single DLLs, and all tests I have been used to so far were in 
one single process. I would have to test what happens if there is one process 
requesting exclusive ddraw access and once process requesting explusive d3d9 
access at once, and maybe a third process doing a screen resolution change, 
etc.

Is there a way to write a test accross multiple libraries? I guess it is not 
hard to do, but it would look a bit bad if a ddraw test started using d3d9 
directly. And is there a prefered way to spawn new processes and do 
communication between them? (Windows IPC I guess).

[Attachment #5 (application/pgp-signature)]



[prev in list] [next in list] [prev in thread] [next in thread]