In presenting the commercial value of wine and why we chose to use it, etc.
How much time do I have for the presentation?
-----Original Message-----
From: Jakob Eriksson [mailto:jakov(a)vmlinux.org]
Sent: Thursday, March 31, 2005 11:20 PM
To: wineconf(a)winehq.org
Cc: Wine Devel; Charles.W.Stevenson(a)guptaworldwide.com
Subject: Re: WineConf Agenda
Brian Vincent wrote:
>I think a full agenda would be about 11 items. If you would like to
>present something let me know - there's definitely space available.
>If you've been wondering, "There's a neat project I'd like to do if I
>could only get a few more people interested", well, this is the
>perfect time to bring it up. If there's something strategic to Wine
>development, this is a great time to discuss it.
>
>
I don't know if I can find the time to prepare a proper
presentation, but if I do, I'd like talk about and get some
input from you on the subject of testing.
1) I want the conformance tests done faster. (I have a clear idea how.)
2) What's almost never been brought up on wine-devel is the
unit testing in the XP sense.
1 has been discussed on wine-devel quite a bit, so I'll skip it
in this mail.
regarding 2:
CXTest is like application testing. This is good, high-level testing.
The conformance tests test the Windows API.
But in the case of a complicated API (and Windows is complicated) maybe
we need to test the smaller units behind the API.
So, the conformance tests often are somewhere between application testing
and unit testing.
Can we have an infrastructure for running unit tests of small units of code
private to the implementation?
I.e. these tests, we could call them "private tests", would not run on
Windows, but
during build of Wine.
Would it be acceptable to just include extra test code in the
implementation c file,
surrounded by #ifdef COMPILE_PRIVATE_TESTS ?
regards,
Jakob
On Fri, Mar 25, 2005 at 11:11:04AM -0600, Alexandre Julliard wrote:
> Modified files:
> windows : scroll.c
> dlls/x11drv : scroll.c
> dlls/user/tests: win.c msg.c
>
> Log message:
> Rein Klazes <wijn(a)wanadoo.nl>
> ScrollDC and X11DRV_SCROLLDC should scroll only pixels coming from
> within the visible region, clipped to the clipping region if that
> exists. Add the destination of pixels coming from the outside of this
> region to the update region. With tests that depend on this.
>
> Patch: http://cvs.winehq.org/patch.py?id=16854
Unfortunately, this patch doesn't fix bug 1091:
http://bugs.winehq.org/show_bug.cgi?id=1091
--
Dimi.
Ivan Leo Puoti wrote:
> Mitchell Mebane wrote:
>
>> Hey there,
>>
>> I ran it on my XP Pro SP2 desktop and Windows Server 2003 under
>> VMWare just fine, but when I ran it on Win2K Pro SP4 under VMWare, it
>> told me the log was too large (6.4 MB > 1 MB) and it would only send
>> partial results. Is there any reason this log would be almost an
>> order of magnitude larger than the others?
>>
> From the log it appears to be a problem with the PathIsValidCharA API,
> you may want to report this to wine-devel.
>
> Ivan.
>
> .
>
OK, I'll do so.
Results are on this page: http://test.winehq.com/data/200503311000/
Specifically, this:
http://test.winehq.com/data/200503311000/2000_mmebane/shlwapi:path.txt
The OS setup I ran the test under is pretty much a bare-bones Win2K Pro
SP4 install. If you want any more information about it, let me know.
--Mitchell
--
The roots of education are bitter, but the fruit is sweet.
--Aristotle
