Question on writing a testcase..

chris ahrendt celticht32 at yahoo.com
Tue May 12 12:12:42 CDT 2009


Paul Vriens wrote:
> chris ahrendt wrote:
>> I have two test cases for the file.c test in kernel32 to show two 
>> problems I have found and reported as bugs that wine should be able 
>> to handle.
>>
>> first problem :
>>
>> I/O warning : failed to load external entity 
>> "file:///C%3A/Program%20Files/Sony/Station/LaunchPad/PatchCache2.xml"
>>
>> Wine does not seem to be parsing this correctly while the various 
>> windows platforms do correctly.
>> So I would like to put a test for this in the test case.
>>
>> Second file issue I found that needs a test case :
>>
>> I/O warning : failed to load external entity "EQ/updatestatus.xml"
>>
>> It seems wine is expecting a fully qualified path in this case where 
>> as windows uses the application running directory and then looks 
>> there...
>> I am not even sure where this is looking in wine.  I would guess at 
>> the root level from the z: mapping if I had to venture a guess 
>> instead of the current running directory.
>>
>> Would I just write the two subroutines and then submit them to 
>> wine-patch?
>>
>> Chris
>>
>>
> What function(s) are the tests for? Did you already write some 
> testcases and run them on Windows?
>
> -- Cheers,
>
> Paul.
>
>
They are for the open file api let me find the exact API.. filehandle = 
_lopen( filename, OF_READ ); in the dlls/kernel32/tests/file.c
I also would write the test for _lcreate and the other couple of API's 
that return a file handle.  And I am using an application on
windows already that does the open in this manner... but could hack 
something out really quick.

Chris






      



More information about the wine-devel mailing list