In software testing, open testing involves publicly releasing a product to a wide audience for testing and feedback, while closed testing restricts access to a select group of users to maintain confidentiality and control.
At BetaTesting, all tests by default are private, secure, and closed. We take pride in this and ensure our clients privacy and security comes second to none. During the invitation process for testers, you have full control to decide how much information about your product and your test to share with them. We privately invite users in batches that match your target audience, and only accepted users receive full test instructions and product access details. The test and all its details remain inaccessible to everyone else, and testers cannot search or in any other form get access to the test.
As part of the sign up process on our platform all testers agree to confidentiality under BetaTesting’s terms, including all of your test details and the existence of your test. This helps to ensure your test remains secret.
On top of the privacy and security provided through the BetaTesting platform itself, we offer additional privacy and security layers at test level:
Custom Screening Surveys: Create custom screening surveys that accept or reject applicants based on their responses, ensuring participants meet your specific criteria. You can dive deeper into this article and learn about the Screening Surveys: Screening Participants for Beta Testing & User Research, and how you can apply them in your next test.
Here is an example of a screening survey, it will automatically reject everyone that cannot record the screen and thereby answers with a No.
Document Signing and Non-Disclosure Agreements (NDAs): Get an additional level of security and peace of mind by requiring that testers digitally agree to your terms as part of the test application process. Testers must download, review, and electronically sign the agreement before participating. The NDAs or other agreements can be distributed via PDF and managed through the screening survey. Here is a full article on NDA’s and how you can manage them on BetaTesting (link to article)
Whitelisting Users: Collect emails, phone numbers, or other info from applicants during the screening survey to manually whitelist specific testers, to provide access to your app for closed betas. At BetaTesting we offer the tools to manage this process from start to finish. Please read the article dedicated to Whitelisting Users for Closed Beta Testing
Manual Review of Applicants: Review and hand-pick your testers based on their responses to your screening questions, their demographic and device details, their LinkedIn profile (if the tester has integrated) and their quality history on BetaTesting. Testers are put on a Pending Applicants list for you to manually review, giving you the power to control who you want to have participate in your test. This article explains the entire process of manual review and the actions you’ll need to take: Screening Surveys: Screening Participants for Beta Testing & User Research
These privacy and security layers are designed to provide you with control over your testing process, ensuring that only qualified and trusted individuals participate in your closed beta tests.
App distribution options
BetaTesting supports the most widely used and industry-standard third party app distribution platforms depending on the preference of your development/QA team, including TestFlight, Firebase, Google Play, and more. We have a full article on App distribution options on BetaTesting for iOS & Android apps that you can explore.