Each one in a thousand: again about Testflight
It's hard to find an iOS developer who has never used TestFlight to test their applications, or at least haven't heard about it. Its popularity in February of this year was confirmed by Apple itself, having bought the company Burstly, thanks to which TestFlight appeared in due time.
As you know, Apple is not one of those who throws money to the wind - on September 9, Apple introduced TestFlight in the App Store under its own brand.
')
Until last week, some developers could use the service by downloading the application, after the release of iOS 8.1 made the tool publicly available, greatly expanding the number of beta testers that each developer can invite by sending them invitations via iTunes Connect from their email address.
The Developer Center website has opened a special section TestFlight, which officially became part of the toolkit for developing iOS applications and the main resource for beta testers, where they can directly download new builds of tested games and applications from the application and send reports. The main differences from TestFlight, which we used, and a year or two ago:
For testers:
After receiving an invite for beta testing applications in TestFlight and using the link, testers download the official service application from the App Store, bypassing the search and sending to the developer UDID device to participate in testing and then install a special profile on your device. The appearance of the new build of the application under test will also be notified by TestFlight (previously, email messages were used for this purpose).
For developers:
The developer can simultaneously test up to 10 different applications. When downloading beta builds from Xcode, we add the names and emails of future testers who are invited to iTunes Connect. Instructions for preparing the beta and setting up a sheet of testers in the video tutorial - here and here .
Testers are divided into two groups: internal (25 team members and trusted representatives with broader technical authority, each can use up to 10 devices) and external - all the rest.
As soon as the developer considers the application ready for external testing, he invites up to 1000 new testers. The developer can open the application to thousands of third-party beta testers after passing the Beta App Review, which confirms the compliance of the App Store Review Guide program being tested - that is, the rules are the same as for publishing user versions of applications. To test on your own, the developer is not required to send the application to the Beta App Review.
Pros:
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 bell tower is able to tell what your application may be just very lacking.
As you know, Apple is not one of those who throws money to the wind - on September 9, Apple introduced TestFlight in the App Store under its own brand.
')
Until last week, some developers could use the service by downloading the application, after the release of iOS 8.1 made the tool publicly available, greatly expanding the number of beta testers that each developer can invite by sending them invitations via iTunes Connect from their email address.
The Developer Center website has opened a special section TestFlight, which officially became part of the toolkit for developing iOS applications and the main resource for beta testers, where they can directly download new builds of tested games and applications from the application and send reports. The main differences from TestFlight, which we used, and a year or two ago:
For testers:
After receiving an invite for beta testing applications in TestFlight and using the link, testers download the official service application from the App Store, bypassing the search and sending to the developer UDID device to participate in testing and then install a special profile on your device. The appearance of the new build of the application under test will also be notified by TestFlight (previously, email messages were used for this purpose).
For developers:
The developer can simultaneously test up to 10 different applications. When downloading beta builds from Xcode, we add the names and emails of future testers who are invited to iTunes Connect. Instructions for preparing the beta and setting up a sheet of testers in the video tutorial - here and here .
Testers are divided into two groups: internal (25 team members and trusted representatives with broader technical authority, each can use up to 10 devices) and external - all the rest.
As soon as the developer considers the application ready for external testing, he invites up to 1000 new testers. The developer can open the application to thousands of third-party beta testers after passing the Beta App Review, which confirms the compliance of the App Store Review Guide program being tested - that is, the rules are the same as for publishing user versions of applications. To test on your own, the developer is not required to send the application to the Beta App Review.
Pros:
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 bell tower is able to tell what your application may be just very lacking.
Source: https://habr.com/ru/post/241714/
All Articles