winetest experience

[Jeremy White]

Okay, so I boldly tried to use winetest with what documentation
I could find, and had an...um...interesting time.

I created these files:

[jertop] cat build.id
fcccd9fca605d1d4c462df5c33f4bacf03bdda5f
[jertop] cat build.nfo
A Large Shovel
[jertop] cat tests.url
http://www.IDontKnowWhatURLToPutHere.com/
[jertop]

did a make dist, and then did:

./winetest -c -t "jw-etch32"

It ran, did it's thing, and had one interactive thing
(Gecko fussed at me; that's not a Winetest bug afaik).

Then when it was all done, it transferred my nearly
1 MB file, and then errored out with:
  "Unknown build id"

So then I looked at the output file, and sure enough, it had
a - for build info, not my fancy git id.

So I hacked that, put in jwtip, and then ran winetest -s
to send my output file through.

And then I have a lovely result here:
  http://test.winehq.org/data/jwtip/

So that's *something* at least.  Although I suspect someone will now
have to go clean up my mess :-/.

So...what's the convention for build.id etc?  And
why didn't they get set?

Cheers,

Jeremy

[Reece Dunn]

On 05/02/2008, Jeremy White <jwhite(a)codeweavers.com> wrote:
> Okay, so I boldly tried to use winetest with what documentation
> I could find, and had an...um...interesting time.

The easiest thing I found for generating test results on Wine is to
treat it like Windows. That is, download the
winetest-[buildid]-paul-mingw.exe from the build you want to test and
run:

   wine winetest-[buildid]-paul-mingw.exe

e.g. on the http://test.winehq.org/data/200801301937/ page, the "Main
summary for build 200801301937", and downloaded
http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/winetest-200801301937-....
Then, I ran

    ./wine winetest-200801301937-paul-mingw.exe

from a build of wine-0.9.54 and followed the instructions on the
program. It did generate an error about not being able to clean the
log at the end, but it generated the "XP wine-0.9.54-notheme" and "XP
wine-0.9.54" results without any issues.
> So...what's the convention for build.id etc?  And
> why didn't they get set?

Looking at the results from the Wine Test Shell, it is using a build timestamp.

- Reece

[Reece Dunn]

On 05/02/2008, Jeremy White <jwhite(a)codeweavers.com> wrote:
> Okay, so I boldly tried to use winetest with what documentation
> I could find, and had an...um...interesting time.

I have added my experiences to the wiki
(http://wiki.winehq.org/ConformanceTests) with a link on the main
page.

Feel free to update it with your own experiences

- Reece