Now, click Add External Testers from the menu on the left. App Store Connect asks you to create a new testing group. You can have one group for all your testers, different groups for different types of testers or different groups for different apps. You can choose between adding new testers manually, adding existing testers — people already testing another one of your apps or builds — or importing testers from a CSV file.
Choose Add New Testers and click Next. Add the email addresses and first and last names of any external testers you want to add. Each person you add counts toward your limit of 10, external testers.
You now need to select a build for your external testers to test. For example, your internal testers might test your master build, while your external testers test your next release candidate. By making you select builds independently for internal and external testers, App Store Connect allows this kind of separation. You can also use this to select different builds for different testing groups.
App Store Connect may ask more questions, such as whether the app requires sign-in or not. Automatically notify testers is already checked.
Uncheck this box if you want to manually notify testers when a build is available. Once complete, click Submit for Review. App Store Connect adds your app to the review queue and changes its status to Waiting for Review. To get approval, your build must comply with the App Store Review Guidelines. Approval usually takes no more than 48 hours. If you checked the Automatically notify testers checkbox, your external testers will receive notification emails at this point.
Your external testers will then receive an invitation email. Instead of adding external testers by email, you can create a public link that allows anyone to install the app. This link works exactly the same way the invitation email does: The tester will have to open it on the target device. In one sense, the link is more convenient than the invitation email.
But be careful when sharing it! Testers invited through the link count against your 10,tester limit, but you can set your own limit to reduce the number of people who can get the app through the link. Both internal and external testers receive similar emails from TestFlight. This email will invite the user to view the app in TestFlight.
The link looks a little different in that it lays out the two steps: downloading TestFlight and app installation. When a new build is available, or when you add a new tester, the tester receives an invitation to test the build via TestFlight.
Then users will see an app preview page. This will show the app icon, build number and the testing information you provided. The screen will look something like this:. After tapping Install , the app will download and appear on the home screen. Now, users can treat it like any other app. This is a handy reminder to the tester of what to look for and how to provide feedback. From now on, whenever a new version of this app is available, users will see a notification from TestFlight. Participants are external testers who are unfamiliar with the app and are trying it for the first time in real-world scenarios.
At this stage, the app is almost ready to launch. Learn more about alpha vs. Cost: Catching bugs before release. More Testers: Uncovering bugs that slipped through earlier test phases, since more testers means a greater diversity of device environments and use patterns.
Diverse Perspectives: Collecting a broad spectrum of feedback with diverse perspectives from users of different backgrounds, demographics, and locales. Bugs and Crashes: Discovering problems with your app that you need to fix or optimize before launching your app.
Learn more details about why you need an iOS beta testing tool. Studies have shown that only one out of five beta testers will try your app and provide you with feedback, and you need a minimum of testers to ensure that your app is properly and thoroughly tested. Learn about dogfooding your app as an alternative to recruiting external beta testers. Beta Family: A crowdtesting community for beta testing where you can test your app on real people and get an honest opinion on the user experience and filter by age, gender, nationality, device, OS and more.
Twitter: Find testers using the common hashtags betatesting , betatesters , testmyapp , indiedev , mobileapptesting , and gamedev and gametesting for mobile games, or scout for potential testers by checking several public Twitter lists that have been compiled by other apps. Betalist: A community of makers and early adopters showcasing their startups and exchanging feedback.
Quora: Most early adopters and influencers can be found answering questions on Quora, so make sure to reach out to them, engage with them, and get their feedback about your app.
Submit your app to ShowHN, but make sure to follow the rules. Killer Startups: A news site that accepts submissions for review. UserTesting: Provides an on-demand human insights platform that helps you find and connect with the exact audiences you need, without the effort, to provide feedback.
UserZoom: The most comprehensive UX insights platform on the market. Betabound: Collects, organizes, and offers beta testing opportunities in an ongoing stream. The biggest problem with iOS app beta testing that mobile app developers and product managers report is not getting enough useful feedback. To discover the insights you need, you need to ask your beta testers the right questions. For example:. All we hope is that Google doesn't let us down with Fabric's 2.
Another great solution that stands out is Applivery, mainly because of its customizability when distributing your builds, which makes it a great solution if for enterprise distributions those that are not meant to be distributed in the public app stores.
Platforms: It supports both native and hybrid apps on both Android and iOS platforms, under any programming language supported by those platforms. It also allows uploading apps automatically, directly from your build server, being prepared to use Bitrise, Jenkins, Travis-CI or any other continuous integration, deployment and delivery platforms.
To top on that, it even provides a Fastlane plugin that will deploy everything with the touch of a button, just like its competitors. Sending feedback or bug report is as easy as taking a screenshot when using Applivery, so it adds on great usability. Popularity: Since it's a recently founded startup in Spain, it isn't as popular as the previously mentioned solutions, but it's definitely a strong competition to the market, due to its enterprise-focused solutions.
For more information on the other plans, see their pricing table. If you have some budget to invest on your project, my personal favorite is definitely buddybuild. With an outstanding range of integrations, auto provisioning profiles management, huge platforms support, and a full continuous integration and deployment support, it just makes sense why all those top tier companies are using it.
Popularity: As stated in their website: "Some of the world's most respected brands trust buddybuild" and I wouldn't change a single word. If you're developing hybrid solutions, they also support any hybrid development framework like Ionic, React Native, PhoneGap, and more.
It doesn't require any configuration setup, scripts or files upon setup, so everything is as smooth as possible when getting everything ready to go. Ease Of Use: When it comes to ease of use, definitely this is one of the most outstanding solutions on the market. Again, with their words: "buddybuild ties together continuous integration, continuous delivery and an iterative feedback solution into a single, seamless platform" and works absolutely beautifully.
And remember the UDID handling mentioned in the beginning of this article? Buddybuild handles everything for you, so you don't have to worry about it. When it comes to the feedback phase, your beta testers can report bugs and give feedback simply by pressing the screenshot shortcut on the device, and even highlight an area in the screenshot if he wants to. Additionally, with every bug or crash report, an instant replay is available for your to analyze, giving you an image on how to reproduce that specific bug.
Misc Pros: What is even cooler about them is that they can send you a quick demo so you can see how easy it is to get everything working. They email you a beta version of a demo app so you can play with it, find out bugs or crashes and report feedbacks. The only bad thing about it is that I personally spent 25 minutes playing when I first received the demo app. Higher plans can be found in their pricing page. Highlight: AppBlade is a Mobile Device Management tool, thus it's a beta distribution tool with a focus on security.
You can remotely install, update and uninstall apps into your devices, as well as secure them, add a layer of encryption, and wipe info from the devices, everything remotely via its dashboard. Highlight: Both of these services register your testing devices connecting to Apple Developer Portal, so they auto-manage your UDID, handle your provisioning profiles and update your IPA automatically.
If your business constantly uses new testing devices or testers, this is definitely the feature you were looking for. You can find their pricing table here. Installr on the other hand has a really limited free tier , and charges "per app". You can run the app on your own iPhone through Xcode. Step A: Add devices to the Provisioning Portal Send an email to each beta tester with the following message: To get my app on onto your iPhone I need some information about your phone.
Click on the below link and install and then run the app. Please send it to me. Collect all the UDIDs from your testers. Go to the section Devices. Click on the button Add Devices and add the devices previously collected. The dialog that pops up should aready have your email and name it it. Select the radio button Saved to disk and Continue. Save the file to disk. Go to the section Certificates. Go to the tab Distribution. Click the button Request Certificate.
Click the button Aprove. Refresh your browser until the status reads Issued. Doubleclick the file to add it to the Keychain. Go to the section Provisioning. Click the button New Profile. Select the radio button Ad hoc. Select the app id.
I have a common app id to use for multiple apps: Evertsson Common. Select the devices, in my case my own and my tester's. Refresh the browser until the status field reads Active. Click the button Download and save the file to disk. Doubleclick the file to add it to Xcode. Step C: Build the app for distribution Open your project in Xcode. Go to the tab Configuration. Select the configuration Release. Click the button Duplicate and name it Distribution. Close the Project Info pane. Go to the tab Build.
Select the Configuration named Distribution.
0コメント