winetest.exe no results

[Tony Lambregts]

Eric Pouech wrote:
> Tony Lambregts wrote:
> > Eric Pouech on  Sunday, September 14, 2003 10:46 AM  wrote
> >
> >
> >>>Eric since you wrote the test could you shed some light on it.
> >>
> >>I think the wrapped tests should fail: MSDN states that wrapping isn't
> >>supported in 95/98 (the test/console.c believes it's always supported)
> >>
> >>but this testSimple() should work in all cases
> >>
> >
> >
> > I don't grep what you mean. What is this testSimple()
> it's the name of the function which fails at line 128 in test/console.c
>
Ah...  But it's name is testWriteSimple()
this is what I see in CVS..

113 static void testWriteSimple(HANDLE hCon, COORD sbSize)
114 {
115     COORD               c;
116     DWORD               len;
117     const char*         mytest = "abcdefg";
118     const size_t        mylen = strlen(mytest);
119
120     /* single line write */
121     c.X = c.Y = 0;
122     ok(SetConsoleCursorPosition(hCon, c) != 0, "Cursor in upper-left");
123
124     ok(WriteConsole(hCon, mytest, mylen, &len, NULL) != 0 && len ==
mylen, "WriteConsole");
125     c.Y = 0;
126     for (c.X = 0; c.X < mylen; c.X++)
127     {
128         okCHAR(hCon, c, mytest[c.X], TEST_ATTRIB);
129     }
130
131     okCURSOR(hCon, c);
132     okCHAR(hCon, c, ' ', DEFAULT_ATTRIB);
133 }

at line 121 c.X and c.Y are set to 0 and line so I would expect that the
output should be at the TOP-RIGHT corner of the screen. However what I am
seeing is that the ouput for this is showing up at the TOP-LEFT (less 3)
corner of the screen.

So I see abc at the top right hand corner of the screen and the test is
locked up under Windows 9x. Pressing CTRL-C allows the test to continue.


> agreed. My point was that I could some other tests in console.c to fail
> under win98, but not this one.
> Does the same behavior happens if you redirect the output to a file
> instead of printing it on screen

I have attached the results of the test that I ran like so:

kernel32_crosstest.exe console > results.txt

I get the same results if I run it in a DOS box  or Full Screen. From the
results and behavior of the test I have to wonder what is the actual value
of c.Y.

Perplexed....

Tony Lambregts





-------------- next part --------------
abcdefgconsole.c:128: Test failed: At (0,0): expecting char 'a'/61 got ' '/20
console.c:128: Test failed: At (0,0): expecting attr 0012 got 0007
console.c:128: Test failed: At (1,0): expecting char 'b'/62 got ' '/20
console.c:128: Test failed: At (1,0): expecting attr 0012 got 0007
console.c:128: Test failed: At (2,0): expecting char 'c'/63 got ' '/20
console.c:128: Test failed: At (2,0): expecting attr 0012 got 0007
console.c:128: Test failed: At (3,0): expecting char 'd'/64 got ' '/20
console.c:128: Test failed: At (3,0): expecting attr 0012 got 0007
console.c:128: Test failed: At (4,0): expecting char 'e'/65 got ' '/20
console.c:128: Test failed: At (4,0): expecting attr 0012 got 0007
console.c:128: Test failed: At (5,0): expecting char 'f'/66 got ' '/20
console.c:128: Test failed: At (5,0): expecting attr 0012 got 0007
console.c:128: Test failed: At (6,0): expecting char 'g'/67 got ' '/20
console.c:128: Test failed: At (6,0): expecting attr 0012 got 0007
console.c:131: Test failed: Expected cursor at (7,0), got (0,0)