Am Dienstag, 26. Juni 2007 17:02 schrieb Anatoly Lyutin:
> 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.
Usually in that case the exact result in not important, since applications
canno
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
Am Donnerstag, den 21.07.2005, 19:32 +0200 schrieb Paul Vriens:
> Wouldn't it be nice if tests accompanied these fixes? Do we have some
> guidelines in this?
I can't find any guidelines for this.
> I know that writing tests is not everybody's hobby.
I doesn't kne
Hi,
I've noticed that in the past weeks there were several patches that
contained a remark like:
- checked on on windows
- compared with native
- ...
Wouldn't it be nice if tests accompanied these fixes? Do we have some
guidelines in this?
I know that writing tests is not everybo
On Wed, 27 Oct 2004, Walt Ogburn wrote:
[...]
What is the reason for this difference? Which example should new tests
follow? My guess is that LoadLibraryA and GetProcAddress are used if the
headers, DLLs, and APIs might not be present on some Windows machines, so
that the tests don't fail.
If the
Hi folks,
I have a question about dependencies when writing tests. Some tests use
LoadLibraryA and GetProcessAddress to get access to Windows / Wine APIs,
and other tests just include the appropriate header files and link to the
DLLs. One example of the first type is dlls/oleaut32/olefont.c