Become a McAfee Beta Tester
Posted by Steven Parker on 30 May 2002 - 16:09 · 19 comments & 10 views
About the Author
Full name: Steven Parker
Forum name: Neobond
Contact: via forum PM
Submissions: Normal · Headline
Full name: Steven Parker
Forum name: Neobond
Contact: via forum PM
Submissions: Normal · Headline
Slashdot It!
Submit to reddit
Submit to blinklist
Bookmark on del.icio.us
Add to furl
Share on Facebook
Add to Windows Live
Add to Google
Beta Programs- Internet Security
- Firewall
- QuickClean
- VirusScan Home
- VirusScan Pro
The Beta department at NAI is dedicated to promoting the testing of Beta software. We aim to ensure that any issues you find are brought to the immediate attention of the Quality Assurance teams. The Beta process at NAI is constantly undergoing change, please feel free to request changes in our working practices or to suggest improvements. Our aim is to ensure that a product ships with no known defects and to improve your knowledge of how a product works so that final installation is seamless.Beta software is released with the specific intention of allowing the customer base to test the forthcoming release against their environment. Pre-release software should not be treated as evaluation software, while it does provide a look at the direction the product is taking, the very nature of the Beta designation implies that the software is incomplete.
You must read & accept the NonDisclosure Agreement (NDA) to be able to participate.
Testing Beta software allows the customer to verify that any defects in the current shipping product are resolved, and that no new defects have been introduced. The earlier in a product's life cycle a defect is found the easier it is to resolve. If you are planning on implementing a product in a production environment, extensively testing a Beta will be a great advantage to you. Not only does it increase your product knowledge, it allows you to bring forward the implementation date. Testing Beta releases also allows you to determine if the software will cause conflicts with your environment before the product is finalized. Defects found at this stage of development are easily rectified before release.