TITLE AND DESCRIPTION
The Title and Description of your test are publicly visible and will be shared with participants invited into your test. The Project Title can be general, such as 'Dating App Bug Test' or more specific, such as 'Tinder iOS App 10.4 Bug Test'.
The Description should give potential testers a high-level explanation of the test, including the goals, requirements, and expectations of the test. For example, "We are looking to find bugs across different iOS devices for this test. You will be asked to create a dating profile, send messages, and test the different settings of our app."
Try to keep your Title and Description short and descriptive to make it easy for testers to quickly understand their expectations for the test.
INSTRUCTIONS / TASKS
The Instructions section is where you can dive deeper into specific features or flows you want testers to complete. You can keep your test more organic, with fewer instructions, or get very specific to have testers focus on exactly what you need tested the most.
For example, you can add one Task only, such as "Please sign-up for our app, explore all of the sections, and try to find as many bugs as possible. Try to focus on messaging and notifications."
Or you can add multiple tasks and have each task focus on a specific feature to make sure testers do a comprehensive review:
Task 1: Sign up for our iOS app.
Task 2: Finish your profile by adding a profile picture and bio
Task 3: Try to create your own group and use the invite feature to email some friends to join.
Task 4: Post some messages and update your notification settings.
Task 5: Logout and try to log back in using the Forgot Password link.
Choose which platform your product is built on - Any Browser, iOS iPhone, iOS iPad, Android Phone, Android tablet, Windows, Mac, or Web. Only testers who have a specific device or OS will be invited into the test.
By default, you will get a mix of devices and operating systems within your chosen platforms. You can target specific OS versions, browsers, or devices by contacting us and choosing our Managed plan option.
LINK TO APP / SITE
Share a link to give testers an easy way to start testing your app. You can link to a specific page on your site, or use a public beta link to send a Testflight link for iOS or Google Play link for apps.
Try to make it as easy as possible for testers to get started to avoid confusion and potential issues getting started.
If you have specific instructions related to getting started, you can add them in this section. Testers will receive instructions when they get invited to join your test.
This can include:
sample email/passwords they should use to login
specific instructions about how to find your app in the App Store
instructions to use social logins or other features
any other instructions testers might need to completely onboard after logging in, e.g. 'complete the dating profile assessment after logging in'
TIME REQUIRED TO COMPLETE
Select how much time testers will approximately spend testing your product, depending on how many tasks you added. The time required to complete a test will affect how much you need to incentive testers.
INCENTIVES PER PARTICIPANT
Choose how much each tester will be paid for completing your test. We recommend a minimum incentive based on your tasks and time required to complete a test.
An average incentive for single-session tests for simpler apps is $10-$15. $10 is the minimum incentive required to recruit testers.
If you are asking testers to complete more complicated tasks, such as connecting to other accounts or sharing more sensitive information, you might need to provide incentives of $30-$50 to guarantee maximum participation.
You will only be charged for participants who complete your test. BetaTesting charges a small fee per completed tester to process payments (greater of $2/tester or 3.5% of total incentives).
After building your test, you will be able to select demographic targets and add a screening survey on the next page.