Computer Chess Club Archives


Search

Terms

Messages

Subject: Re: The privilege of beacoming a beta-tester

Author: Gordon Rattray

Date: 20:06:22 09/05/00

Go up one level in this thread


After reading the various threads so far, I'd add the following...

An important factor relates to what the beta testing involves.  In particular,
how formal does the beta tester perform the testing?  Some people suggest that
they just use the program as they normally would.  However, others may make more
of an attempt to systematically cover as much functionality as possible.

I can understand why the former approach can offer the tester enjoyment and
hence they too are benefiting.  However, if the testing is more formal, I don't
believe that anyone would consider this to be generally a pleasure and it
certainly would not be a privledge.  Systematically going through each and every
menu option, dialog box, etc. is a tedious task if done properly.

So, if I'm given a program and told "just have some fun with it", I'll genuinely
say "thanks" and do just that.  But if I'm obliged to do some more formal
testing, then while I may still accept the deal, I wouldn't expect the
programmer to think that they are doing me a huge favour as in this case I think
the tester is doing the programmer more of a favour.  Remember, I'm talking
about the task of performing formal and quality testing of the program - totally
different from "just using it".

If a formal approach is required, then whether an individual requires payment is
up to them and the programmer can decide whether it's worth paying.  I
personally would make some effort off my own back, but I would expect the
programmer to at least acknowledge this effort and not think that I owe them.

Finally, many people in this newsgroup (including myself) pay a lot of attention
to the playing strength of a program.  However, no matter how strong a program
is, we still expect it's overall functionality to work when we pay money for it.
 So, whatever strategy programmers decide to take when testing their programs,
they have to accept that cutting cost/effort in this area can affect user
satisfaction of the product.  For example, I don't like having to download an
update in order to get some fundamental analysis functionality working.  This is
only acceptable for engine updates and minor enhancements where the user can
choose not to update.

Gordon



This page took 0 seconds to execute

Last modified: Thu, 15 Apr 21 08:11:13 -0700

Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.