|
|
| Home | Our services | Latesst news | Our features | Favourite links | Contact us |
|---|
How can I beta
test Microsoft products?
What is a Beta
Tester?
Before software gets
released to the public, it goes through certain testing phases. The first phase,
called the alpha test, is preliminary, limited internal testing for
functionality and stability. Alphas generally do not get released to the
public.
Beta software is software that has already been through the alpha
testing process, and is considered by the developer to be stable enough to be
used in a limited number of controlled, real-world situations. That's where beta
testers come in!
Beta testers are people who agree to use a not-yet-finished
product, and to provide feedback to the developer based on their use. Beta
testers need to be willing to use products that have minor and/or major bugs,
and must understand that little or no technical support is offered on beta
programs. If support is offered, it's usually in the form of a message board or
newsgroup dedicated to the beta test.
Public and Private Betas
When software companies offer a beta test, they usually
take one of two approaches: public beta or private beta.
Public betas
programs allow anyone to have access to the software, sometimes by free
download, sometimes by paying a small fee for production of the discs and
shipping. There are a lot of software developers, for example, that release
their software in public beta form in our news page. Microsoft releases a fair
number of public betas on their site, as well.
Private betas programs are
limited to a smaller number of people in a more structured and controlled
environment, and testers must be willing to be very active in reporting bugs and
feedback.
Some software goes through both test programs, releasing the
product to their private beta testers first, to iron out serious bugs, and then
releasing a public beta when the product is a bit more stable, to get more
general feedback from the public.
Signing Non-Disclosure Agreements
Most beta testers are required to sign an NDA, or Non-Disclosure
Agreement, before a company will allow them access to a private beta. By signing
this, beta testers agree to not release any non-public details or private beta
copies of the product to external sources. This is important for security
reasons, and to ensure that the competition does not have unfair access to, or
information about, a developer's new software product.
Unfortunately, there
are plenty of sites on the 'Net that violate their non-disclosure agreements,
and who release non-public information concerning beta products and technologies
to the public. Information about new products is always in demand on the Web,
and these Web sites are willing to trade their integrity for the fleeting
popularity of having "secrets" or a "scoop" about an upcoming product. If this
is what you are hoping to find on WinFiles.com, then you've come to the wrong
place. While WinFiles.com works very hard to keep our visitors informed, we
never have, and never will, release any information that is in violation to
non-disclosure agreements we have signed.
How to Apply for a Microsoft Private Beta
While many public betas can be downloaded
directly from Microsoft, we get a large number of requests from our visitors for
information on becoming a private beta tester for Microsoft, because private
betas are usually released months, or even years, before they enter public beta
testing. Microsoft currently maintains an open beta application process, in
which anyone can apply for a private beta. However, a very small number of
people are accepted for private betas, and there is no guarantee of acceptance.
Microsoft does, however, give preference to previous private beta testers when
releasing new private betas. Once you are on Microsoft's private beta tester
list, you will be contacted from time to time with applications for private beta
test programs, according to their needs and your system configuration.
To
submit your name for consideration for Microsoft private betas, send an email to
betareq@microsoft.com, with the
information below. The subject of your mail should be the name of the product
you are interested in beta testing. If you are interested in testing multiple
products, you must submit a separate e-mail for each product of interest so that
they can quickly filter your request to the product team handling this program.
If the subject contains anything other than one beta product name, it will
automatically be deleted by Microsoft's mail servers! Do not put "Microsoft" in
the subject line.
Name (First, Middle Initial, Last)
Company
Street Address (no PO Boxes)
City, State or Country, Zip
Phone
Fax
Internet address
Product interested in beta testing (if more
than one, please submit separate e-mail requests)
Brief description of your
hardware configuration.
Have you been a beta tester for Microsoft? If yes,
then list product(s) that you've tested. Please briefly describe your past or
present beta experience and how you will be using or applying the product(s) you
are interested in testing.
After the above information had been received, it
will be forwarded to the specific product group for review and consideration.
Due to the volume of requests Microsoft receives, you will be contacted only if
selected to participate in the beta program.
Make sure that you are honest
when describing your hardware configuration. Don't think that by overstating
your system's properties that you will have a better chance at acceptance. In
fact, as a former employee of Microsoft, I happen to know that they are flooded
with beta requests from users with powerful CPUs and lots of RAM, and that
they're looking for users with average systems. Because they sell their products
to a wide variety of users, Microsoft is looking to test their products on a
wide variety of systems, so tell them exactly what you have, even if it's not
something you'd want to brag about.
When All Else Fails
If you don't get a response from the above email address (and most
people don't), there are still a few ways you can get access to "limited"
release betas. They're not exactly private betas, but you can get beta products
faster than waiting for the public betas.
First, if you attend a
Microsoft-sponsored developer's conference, seminar, or training session, you'll
usually get a few betas of the products related to the conference.
Second,
try attending conventions where Microsoft is a participant, like COMDEX, or
Internet World. They'll usually pass out beta software there, too.
Finally,
keep your eye on the Microsoft Web site for what Microsoft calls Preview
Programs. They're large-scale beta programs where Microsoft makes available a
limited number of beta copies to people who request them. The Windows 95 Preview
Program, for example, was sent to 400,000 testers around the world who paid
$39.95 to join the preview program. A similar program was offered prior to the
release of Internet Explorer 4.0. Microsoft usually makes a toll-free phone
number or a secure Web site available to join these
programs.
A Final Word of
Advice
That's it! I hope
you're successful in joining a beta program. A word of advice before I finish,
however. If you download private beta software without being on the private beta
team, you're actually downloading and using pirated software. Many times, beta
software makes it's way around pirate FTP sites, Web sites, and newsgroups, but
the risks of downloading software from these sources far outweigh any benefits
of accessing beta software. If you download a beta from anywhere other than the
developer, you're running the risk of computer virus infection, corrupted files,
or even complete system failure - not to mention criminal and/or civil
prosecution from the developer. It's not worth the risk, and it's not worth
trading your honesty for. My advice is to apply to join a legitimate beta
program, or wait for the released product. Good luck!