One Thousand: Once More About Testflight

    It is difficult to find an iOS developer who has never used TestFlight to test his applications, or at least not heard of him. Its popularity in February this year was confirmed by Apple itself, having bought the company Burstly, thanks to which at one time appeared TestFlight.

    As you know, Apple is not one of those who is throwing money away - on September 9, Apple introduced TestFlight in the App Store already under its own brand.

    Until last week, some developers could use the service by downloading the application, after the release of iOS 8.1 they made the tool publicly available, significantly expanding the number of beta testers that each developer can invite by sending them invitations via iTunes Connect from their email address.

    A special section TestFlight has opened on the Developer Center website, which has officially become part of the toolkit for developing iOS applications and the main resource for beta testers, where they can download new builds of tested games and applications directly from the application and send reports. The main differences from TestFlight, which we used a year or two ago:

    For testers:

    Having received an invite for beta testing the application in TestFlight and using the link, testers download the official service application from the App Store, bypassing the search and sending the developer UDID device for participation in testing and the subsequent installation of a special profile on your device. TestFlight will also notify you of the appearance of a new build of the tested application (previously, e-mail messages were used for this purpose).

    For developers:

    A developer can simultaneously test up to 10 different applications. When downloading the beta build from Xcode, we add the names and emails of future testers, whom we invite to iTunes Connect. Instructions for preparing the beta and setting up the testers sheet in the video tutorial are here and here .

    Testers are divided into two groups: internal (25 team members and especially proxies with wider technical powers, each can use up to 10 devices) and external ones - all the rest.

    As soon as the developer finds the application ready for external testing, he invites up to 1000 new testers. The developer gets the opportunity to open a thousand third-party beta testers after passing the Beta App Review, confirming the compliance of the tested App Store Review Guidelines program - that is, the rules are the same as for publishing custom versions of applications. For in-house testing, the developer is not required to submit the application to the Beta App Review.


    The more testers, the better. Now you can test the program with the help of not only a fairly narrow circle of sophisticated experts, but also a wide user audience, each of which with its own bell tower is able to tell what your application may be just missing.

    Also popular now: