Janitorial Projects -- conformance tests --recruiting volunteers
Tony Lambregts
tony_lambregts at telusplanet.net
Tue Dec 10 00:43:05 CST 2002
Francois Gouget wrote:
>So what I did is compile them here, whip up a quick batch file to
>invoke them all, and zip them up. You can download them from:
>
>http://fgouget.free.fr/wine/winetests.zip
>
>
>Just unzip them in some random directory and run them as follows:
>
>runtests.bat
>
>
>The above script skips the generated tests (for no particular reason)
>and skips the sysparams user32 test because it messes the environment
>badly (e.g. the width of window borders).
>
>Given the number of tests that fail you may want to run them one by one
>to better capture their output. To do so just have a quick look at
>the batch file, running the tests is very easy, e.g.:
>
>kernel32_test.exe path
>
>
>
>
[snip}
I started a bug report http://bugs.winehq.com/show_bug.cgi?id=1185 for
the conformance test not running on windows 98
Runing the tests on Microsoft Windows 98 (4.10.1998) a lot of tests fail. tests
downloaded from http://fgouget.free.fr/wine/winetests.zip
I was unable to redirect the output of the tests to a file. For example
"ws2_32_test.exe sock > temp.txt" would give me a 0 lenght file is it supposed
to work that way? Some tests output more than 50 lines so that even with the
terminal set to 50 lines I would not be able to copy all of them.
Also a lot (most) of the tests had the prefix of where the file resided on when
it was compiled for each line, which made for very long lines. I cleaned up the
lines wrap, but is it really nessesary to print the whole path.
The output from the tests is at http://bugs.winehq.com/showattachment.cgi?attach_id=350
--
Tony Lambregts
More information about the wine-devel
mailing list