"Why in the world do you beta test software products?" (This is the most often asked question.)

I often ask myself this same question. Some of my reasons for beta testing include: gaining insight into a soon-to-be-released product, and having a chance to provide valuable input during the development of the product. Not only do I gain experience as the software comes together and the developers release subsequent updates, but testing also provides me with a mechanism to enhance the product by sharing my ideas for improvements in the product.

Another reason I beta test software is to evaluate products and technologies that may be beneficial to the future growth of our university network. This helps me plan the future growth of our university network.

"What are the major frustrations of beta testing?"

Ah yes, the frustrations. Beta testing requires time and patience, both of which are often in short supply for system administrators. To compound the arduous task of testing beta software, the time allotted by companies for testing is often relatively short. This is particularly frustrating because it makes it difficult for software developers to communicate bug fixes to me in a timely manner. This often leaves me traveling down a dead-end road, only to find that I have discovered a bug that has already been unearthed and fixed by the developers.

Another frustration of beta testing is what I call "latency." In my experience, software usually evolves through a series of beta releases. As a result, features that I am looking for in a product may not be in the beta version I am presently using or, worse still, the version I have may not even be fully functional. In addition, each subsequent release requires yet another installation cycle.

"What have you learned by being a beta site?"

Software beta testing provides me with many learning opportunities. One of the most useful things I have learned in beta testing software is the ability to diagnose, document, and report problems in beta software and in other "production" software as well. By dealing with developers in beta programs I understand what information is needed to help the software vendor diagnose a problem and provide a quick fix, regardless of the type of software. And, as I mentioned before, beta testing provides me with an excellent opportunity to plot a direction for better growth and utilization of my own network.

"What are the rewards of being a beta tester?"

A big gain is that beta testing a product provides me with time to plan for the installation and deployment of the real production software. When the product is finally release, I can deploy it almost immediately.

I also enjoy contributing to the success of a product by being able to shape its direction, by making sure that the product features I am most interested in work, and by insuring that features work correctly in my network environment.

I also get a kick out of the recognition I receive as a beta tester. This fame often results in additional technical opportunities and the occasional trade magazine interview. One of the nicest rewards of testing software is the recognition I get from a software company itself. This can lead to discounts on the products I've tested, or other free giveaways. For example, by being a beta tester I got to write this article, and for that the SNCT editor generously sent me a Solstice Network Client T-shirt. Man, it just doesn't get any better than that!

"I know it's not for everyone..."

There you have it, my life as a beta tester. At times it feels as if I am constantly beta testing software, whether it is actually beta software or "production" software that was released just a bit too soon. I know that beta testing is not for everyone. On the really bad days, I try to remember that beta testers are a necessary part of the product development cycle. And that without guys like me, the functionality, reliability, and quality of most software products would be, to put it mildly, compromised at best.

bio: Ray W. Hiltbrand is a UNIX System Administrator at Auburn University College of Engineering, Auburn AL. He tests both PC and UNIX server products. E-mail him at Ray.W.Hiltbrand@Eng.Auburn.EDU or visit his homepage.