Writing tests in Wine.

Anatoly Lyutin vostok at etersoft.ru
Tue Jun 26 10:02:10 CDT 2007


Hi all!

When I analyzed Wine test codes today I do not understand how to
interpret result of tests.That is why I refer to community.
I can not find any full documentation for writing tests at WineHq.

I have some points which I do not understand:

1. Why some tests are running in Win not fall if expected and obtained
messages are not coincide.
ex (user32:msg:test_mdi_messages:Win2k3):
msg.c:2716:mdi frame: 00090362, 0086, 00000000, 00000000
msg.c:2716:mdi frame: 00090362, 0002, 00000000, 00000000
msg.c:2716:mdi frame: 00090362, 0082, 00000000, 00000000
msg.c:3302:expected 0004 - actual 0004
msg.c:3302:expected 0046 - actual 0046
msg.c:3302:expected 8003 - actual 0047
msg.c:3302:expected 0086 - actual 0047
msg.c:3302:expected 0047 - actual 0047
msg.c:3302:expected 0086 - actual 0086
msg.c:3302:expected 0006 - actual 0002
msg.c:3302:expected 001c - actual 0002
msg.c:3302:expected 8003 - actual 0002
msg.c:3302:expected 8001 - actual 0002
msg.c:3302:expected 0002 - actual 0002
msg.c:3302:expected 0082 - actual 0082

Why does not this fail?(ok_sequence(WmDestroyMDIframeSeq, "Destroy MDI
frame window", FALSE);)

2. How I can write test for different OS Windows?
Some tests run  successfully in win2k3 but fail in XP, that is why this
test can not be validated by HQ.

3.What does it mean :{ HCBT_SETFOCUS, hook }?

What does this hook in some tests make fail in Win2k3 if it was included?

Thank you for attention.

-- 
Best regards
	Anatoly Lyutin.





More information about the wine-devel mailing list