Thanks to Brian Vincent, Paul Millar, Dimi Paun, Ferenc Wagner and Kevin Koltzau the automated winetest suite is ready for more widespread testing.
Kevin and Paul build winetests each night if there were cvs commits since the last time the tests were built. The winetests are published to a script on winehq that Brian and Dimi wrote. The winrash service that I wrote sends its current state to the service and receives a script to process that may direct it to check in later, download a winetest and run it or upgrade itself. Thanks to Ferenc the winetest results are sent back to winehq and can be accessed via http://test.winehq.org/data/ Pretty formatting of the results is coming soon ;-)
We need volunteers that are willing to particpate in the winetesting process by running the winrash service on their computers. The winrash installer can be downloaded from: http://prdownloads.sourceforge.net/winrash/winrash-0007-chris-msvc.exe?downl...
You can find out more about winrash at http://winrash.sf.net
The installer will install winrash as a service and run Wine tests as required. It is IMPORTANT that you set the client id correctly. Please use your first and last name WITHOUT spaces, like JohnSmith. Using the default client id will cause your winetest results to be ignored.
The service is smart enough to autoupgrade as new versions are released. To uninstall just go to the Add/Remove programs and click 'remove' as you do for many windows programs. There is the ability to restrict the times when winrash runs winetests but this requires manually adding some keys to the registry. I haven't finished testing this feature but if someone wants it I can see about getting it polished up and in a release early this coming week.
We currently need testers for the whole range of windows versions, win95/98/me, nt3/4, win2k, xp and 2003.
Please reply if you want to help out so that we know what kind of coverage we can expect. The more the merrier, so please sign up even if others have done so for your version of Windows.
Chris
Chris Morgan cmorgan@alum.wpi.edu writes:
the winetest results are sent back to winehq and can be accessed via http://test.winehq.org/data/ Pretty formatting of the results is coming soon ;-)
Do you mean somebody's already working on it or that I should do it eventually? I'm back from the summer school but the examination period started here, so I can do some work again. It would even make more sense now that the dust settled. Have you perhaps got concrete ideas? It would be interesting to hear the experience of people using/working from the reports. What's missing, what should be easier? Anyway, thanks for the good work, guys!
On Sat, May 29, 2004 at 09:22:02AM +0200, Ferenc Wagner wrote:
work again. It would even make more sense now that the dust settled. Have you perhaps got concrete ideas?
So here is what's left to do: 1. Finish the metadata-in-winetest patch 2. Arrange the reports on WineHQ 3. Maybe add script signing/checking to winrash/service.cgi (this is optional, and just a nice-to-have ATM).
I'm sure you know precisely what's required for (1), so I'll focus on (2). For that, I was thinking we need a page (http://www.winehq.org/site/status_testing) that is organized into two sections (just like our home page, with "About Wine"/"Latest News").
The first section (let's call this "Wine Testing") would contain a short description of our testing framework, what it does, how you can sign up to become a tester, pointers to where the tests can be downloaded from, etc. This section is obviously hand crafted.
The second section (call it "Test Reports") would contain links to the various reports generated by dissect/gather. This section would me automatically generated. Ideally the section would contain the current and the previous month (in the form of a calendar, as reported cal(1)), with the applicable days being links to the reports. At the bottom of the section we should have a link to a page listing all historical reports (again if possible in the same cal(1) format).
Looking at this, it now seems better if we arrange these two sections one besides the other, like "About Wine" and "Weekly Newsletters" on our home page. Namely, "Wine Testing" will be in the middle, while "Test Reports" will be a narrow section to the right of the page, with the month listed one below the other in decressing order (and BTW, we could display more than 2 months at a time).
How does this sound?
On Sat, May 29, 2004 at 09:22:02AM +0200, Ferenc Wagner wrote:
What's missing, what should be easier?
Now that you're asking: in the reports, I don't quite like that a single report for Win95 is listed as OSR2 in the main summary, but then it switches to Win95(n) when we have more than one. Similarly for Win98. This is very confusing.
For example, after the first submitted tests, the main summary header read:
OSR2 SE ME ....
I wasn't even sure what SE was. Anyway, I think the header should remain immutable:
Win95 Win98 ME NT3 NT4 2000 XP 2003
"Dimitrie O. Paun" dpaun@rogers.com writes:
On Sat, May 29, 2004 at 09:22:02AM +0200, Ferenc Wagner wrote:
What's missing, what should be easier?
Now that you're asking: in the reports, I don't quite like that a single report for Win95 is listed as OSR2 in the main summary [...]
I tend to agree, this idea didn't really work out. Somehow different Win9x subversions have well recognised names like OSR2, SP1, SE but other Windows flavours do not while still having service packs of course. We could probably drop this distinction altogether and empty this layer of abstraction. It would simplify things a bit. Deal?
On Thu, Jun 03, 2004 at 10:50:13PM +0200, Ferenc Wagner wrote:
I tend to agree, this idea didn't really work out. Somehow different Win9x subversions have well recognised names like OSR2, SP1, SE but other Windows flavours do not while still having service packs of course. We could probably drop this distinction altogether and empty this layer of abstraction. It would simplify things a bit. Deal?
Deal. If we do the simple thing and just keep the name constant (i.e. Win95, Win98, etc.) would be perfect. If we need more info, we just click on the link and look at the report.
-
Chris Morgan -
Dimitrie O. Paun -
Ferenc Wagner