Beta Testing








Beta Testing Q & A


Firstly, thank you for your interest in the beta programme. To start with, here are some answers to common questions asked:


Q: What is beta testing?
A: Beta testing is testing a program version that has been already tested by the developers on the reference test environment(s) but requires further testing in many more environments to certify that it works correctly.


Q: Why is beta testing not done by you?
A: What we do is alpha testing on all reference & test systems. The beta testing is additional testing "in the wild" that needs to be done before release.


Q: How stable is the beta?
A: Unknown since you'll most likely be testing on an untested configuration most of the time. However, in the worst case scenario it should not result in data corruption.


Q: Can I use the beta to evaluate the Professional version?
A: No, as it is a beta - not meant to be used for testing. Once the beta programme is finished you can evaluate the release version.


Q: Who can be a beta tester?
A: The entry requirements for the beta programme are similar to other software houses:


Current user of the product in question (not necessarily registered).
Current interest in the product.
Wilingless and free time to test at least one of the beta releases on the test system.
Send at least one report from the test system or comments relating to the performance of the product on the test system [per programme not per version]. You don't have to test each release - if you can, please do!
Technical proficiency to understand what's going on.
Backed up system that does not run mission-critical applications.
A test system that we are looking to test the product on (see requirements).
Not a citizen/national of a country we could not sell/send/ship you a product, i.e. UK/EU/US embargoed countries, or other restrictions.



The following list of people do not need to satisfy the entry requirements:


Previous beta tester of the product.
Employee of computer press (reviewer, editor, tester, etc.).
Employee of computer hardware/software technology partner (or use existing contact).



Q: Who can NOT be a beta tester?
A: We reserve the right to refuse or remove from the beta programme any user that does not adthere to the rules stated. We think the rules are just common sense and such issues should not occur but there is always the possibility. Here are other restrictions:


Users providing a generic e-mail address (e.g. Hotmail, Yahoo, BigFoot, etc.); this way we could not confirm identity.



Q: Will I have to sign a NDA?
A: Generally no, although if the product has technology that has not been officially launched you may need to. You will still be able to beta versions that don't include such technology or after the official launch of the technology.


Q: Can I publish (benchmark) results using the beta?
A: No, unless you have special authorisation. This is granted only if the beta addresses issues that prevent the previous release from being used and the results are similar. Do note that users will be unable to verify your results otherwise before the release is published.


Q: How long does the beta programme last?
A: The beta process is on-going. You can drop out at any point.


Q: How do I drop out?
A: Please go to the Contact Page and send an e-mail to the Beta address stating that you wish to drop out. Your current licenses are yours to keep.


Q: What are the advantages in being a beta tester?
A: Here are some of them:


A complementary copy of (all versions/platforms) the commercial/retail copy of the product, and licenses for your test systems (up to 10). These are full new copies, no need to patch old versions.
Access to all the beta releases and release candidate versions. This includes access to fixes and patches without waiting for the next release.
Free merchandise from our Cool Stuff range of goods with our thanks.
Opportunity to ask for additions/modifications to the features of the product.
Advance information on new features and modifications before release thus allowing you to be ready on release.
Compatibility testing of your products on the current version of our product and resolve any issues before release(s) providing full compatibility.
Acknowledgement in the product itself for your efforts.



Q: How about payment for my efforts?
A: This activity is designed for interested parties that would use the product anyway and do the beta testing as their time allows. It is not designed to be a proper test activity that would be compensated monetarily - although it is compensated (see above). Do note that you are not required to test each and every version but as your time allows.


Q: What configuration do I need to have to become a beta tester?
A: For best coverage, this is posted on the Product Page. Please visit this page for a list of current configurations we're looking to test.


Q: OK, got that, how do I become a beta tester?
A: Please go to the Contact Page and send an e-mail (with your configuration information) to the Beta address.


Thank you again for your interest in the beta programme.