Draft Call for Testing

Dan Kegel · Post by **Dan Kegel** » Wed May 07, 2008 8:13 pm

Hi folks,
how does this look?
http://wiki.winehq.org/PlatinumRegressionHunt
I hope to publicise this once wine-1.0.0-rc1 is released.

Let me know if the instructions are hard to follow.

Thanks,
Dan

Tlarhices · Post by **Tlarhices** » Wed May 07, 2008 8:36 pm

The explanations are good I think, just a few points (mainly personal opinion) :

"even for people who don't know a commandline from a kumquat"
Insulting people even for fun and in a funny way isn't a good idea if you want many inexperienced users to discover wine the "good" way.

Adding a friendly page on "How to fill a test report" and maybe good examples can be helpful to lower the quantity of bad reports.

In the past, test reports was taking a really long time to be accepted, I hope there will be enough people ready to read them for the hunt.

And is there a way to see the platinium rating software without test reports on a specific version of wine ?
Might be useful to limit the quantity of platinium software not going through the test.

Dan Kegel · Post by **Dan Kegel** » Wed May 07, 2008 8:52 pm

On Wed, May 7, 2008 at 6:36 PM, Tlarhices <[email protected]> wrote:

"even for people who don't know a commandline from a kumquat"
Insulting people...

Gee, I didn't think that could be insulting, but you're right, I'll change it.

Adding a friendly page on "How to fill a test report" and maybe good examples can be helpful to lower the quantity of bad reports.

Yes.

In the past, test reports was taking a really long time to be accepted, I hope there will be enough people ready to read them for the hunt.

Yeah, good point, I'll check on that.

And is there a way to see the platinium rating software without test reports on a specific version of wine ?
Might be useful to limit the quantity of platinium software not going through the test.

There are people working on better searching in the appdb, but I
don't know when it'll be ready. It's ok if it's not ready immediately,
but as time goes on and the appdb gets picked over, it would
be helpful. I'll check.

Thanks for the feedback!
- Dan

jeffz · Post by **jeffz** » Thu May 08, 2008 1:01 am

One other thing to think about including in the instructions is if applications are tested and they crash, rather than paste the crash data in the application database which doesn't work very well, maybe that information should be managed somewhere else?

Maybe along with the follow-up post to the forum?

Dan Kegel · Post by **Dan Kegel** » Thu May 08, 2008 6:50 am

On Wed, May 7, 2008 at 11:01 PM, jeffz <[email protected]> wrote:

One other thing to think about including in the instructions is if applications are tested and they crash, rather than paste the crash data in the application database which doesn't work very well, maybe that information should be managed somewhere else?

Maybe along with the follow-up post to the forum?

Complicates the instructions. Let's see how often it happens. They *are*
starting out with platinum apps, hopefully crashes will be infrequent.

Timeout · Post by **Timeout** » Thu May 08, 2008 8:24 am

First, make sure your machine runs glxgears properly (if it crashes, you may need to update your graphics drivers)

A question: I am not playing games on my computer but my graphic card supports 3D.
How can I test this?

Dan Kegel · Post by **Dan Kegel** » Thu May 08, 2008 8:31 am

On Thu, May 8, 2008 at 6:24 AM, Timeout <[email protected]> wrote:

First, make sure your machine runs glxgears properly (if it crashes, you may need to update your graphics drivers)
A question: I am not playing games on my computer but my graphic card supports 3D.
How can I test this?

By running glxgears?

Hmm, if that's not clear from what I wrote, I guess I need to give
better instructions!

Elfe · Post by **Elfe** » Thu May 08, 2008 4:25 pm

a better description for the 3d part is needed (as in 3d running with mesa or with accelerated driver - glxinfo with examples of the used driver would be good)

we shouldn't tell the users to nuke their .wine directory
renaming or teaching how to use WINEPREFIX would be better

vitamin · Post by **vitamin** » Thu May 08, 2008 4:31 pm

Elfe wrote:a better description for the 3d part is needed (as in 3d running with mesa or with accelerated driver - glxinfo with examples of the used driver would be good)

we shouldn't tell the users to nuke their .wine directory
renaming or teaching how to use WINEPREFIX would be better

Actually removing ~/.wine directory is appropriate to get the clean start with RC1. After that it should not be done at all, unless as the last resort.

Dan Kegel · Post by **Dan Kegel** » Thu May 08, 2008 4:39 pm

On Thu, May 8, 2008 at 2:25 PM, Elfe <[email protected]> wrote:

a better description for the 3d part is needed (as in 3d running with mesa or with accelerated driver - glxinfo with examples of the used driver would be good)

Perhaps for 3d apps, that's true. The only reason I mentioned glxgears is
because a few 2d apps need opengl (strange, but true). If some
gaming expert wants to add an addendum for games testing,
please feel free.

we shouldn't tell the users to nuke their .wine directory
renaming or teaching how to use WINEPREFIX would be better

We could mention that as an alternative, but I'm
afraid of complicating those instructions much, they're
already very long.

Tlarhices · Post by **Tlarhices** » Thu May 08, 2008 7:32 pm

Also using WINEPREFIX is great as long as you know how to set environment variables and not double click on the exe file in a file manager. It might be hard for the users the guide is designed for.
You may add some advanced user tips at the end or on another page but keep it simple and short or nobody will read it past the title.

Elfe · Post by **Elfe** » Sun May 11, 2008 6:15 am

I added an entry to the FAQ for the 3D driver/acceleration check