how to join beta testing in the future?

  • Thread starter Thread starter jim
  • Start date Start date
J

jim

Some beta testers got a free copy of vista if they submited bugs... but not all beta testers.

How can I become a beta tester like those who got vista,
for future versions of windows?

thanks
 
If your motivation to become a beta tester for Microsoft is to eventually
be offered free software, you may be disappointed. It takes a lot of work
to test software, observe, reproduce and submit bugs, reformat your hard drive frequently, etc.
It may take up to three years to receive an invitation to become a beta tester
for Microsoft, based on my own personal experience.

P.S. Since Microsoft never mentions if beta testers will receive a complimentary
copy of the released software, there is no assurance you'll receive any released
software. A beta tester for Microsoft is strictly a voluntary effort.

How to apply to become a beta tester for Microsoft
http://support.microsoft.com/kb/833520

--
Carey Frisch
Microsoft MVP
Windows Shell/User

--------------------------------------------------------------------------------------

:

Some beta testers got a free copy of vista if they submited bugs... but not all beta testers.

How can I become a beta tester like those who got vista,
for future versions of windows?

thanks
 
As Sam and Carey indicate, go to Connect and sign up for one or more betas
that interest you. But don't stop there. Contribute to the beta newsgroups
that go with the programs you sign up for and FILE BUGS. Those signed up on
Connect may have an opportunity soon to begin filing suggestions for the
next version of Windows, Windows codename Vienna. Do that too if offered
the chance. Get yourself known in the beta community. There is no single
or simple way to get invited into the TechBeta for the next version of
Windows, but persistence pays.
 
Everyone who submitted one bug and actually submitted got a free copy. If
they didnt get a copy they actually deserve there are people they can
contact. Anyway, sign up for allot of betas on connect and participate and
file bugs in them. Also participate in NGs. There is how ever no garauntee
you will get free copy.
-Cullen Dudas
 
Hi, Jim.

In addition to the caveats from the others...

For anyone "reading over our shoulders" and thinking, "That's an easy way to
get free software", remember...

Beta software is unproven - by definition - and unsupported. You should
have at least two computers: one to use for the beta testing, NOT for any
useful "production" during the beta period; and another computer to get all
your work done. This second one can also be used to get on the Internet or
into newsgroups to get help when your beta machine is fouled up so badly
that you can't even get it to boot. You will also need a way to file bugs
to report exactly what you tried and how you did it and what went wrong -
even if your beta machine can't go online. Remember, your job is not to fix
bugs, but to find and report them so that MS can fix them. If you are an
experienced dual-booter and have loads of unused disk space, you might be
able to pull it off with a single computer, but that's not the smart way to
go.

When testing an operating system, be prepared to reformat your hard drive
several times during the beta period and reinstall everything from scratch
all over again. And be sure you have a way to keep your data backed up on
your production machine, because your beta machine will probably lose
everything at least once.

Good luck. Enjoy your "free" copy of Vienna (or whatever) - if you get one.
You will have earned it!

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP
(Running Windows Mail 7.0 in Vista Ultimate x64)
 
I can see your logic Colin, however an obscure beta cannot provide a high
chance of recognition for a Windows beta.
 
Once you are registered in the Connect database a program manager
constructing a new testing group can find you when they search on beta
tester characteristics, such as whether a tester downloads bits, files bug
reports, participates in beta newsgroups, past betas participated in, and
who knows what else. It isn't just a matter of "getting noticed." Program
managers do filter the database for candidates and they construct structured
testing groups based on percentages of experienced testers, less experienced
testers, novice testers, geographical locations, languages, and so on. They
set these percentages when they develop thier test program objectives.
 
Back
Top