How Can I Add Someone as a Test Without Going Through App Review Testflight

Testing Your App Using TestFlight

There are many types of testing that you can add at unlike phases of your project. Your last line of defense is testing within the final stages of the project—where yous can take hold of those terminal-minute defects that can potentially harm your product'southward use, impairment its value to the user, and tarnish your company'southward reputation as a manufacturer of high-quality items.

Various tools exist to assist you lot during these final stages. One of the virtually well-known tools for testing iOS apps is TestFlight.

If y'all've never used TestFlight, this post will exist an introduction to the tool and will draw how yous can best use information technology during your project to ensure few to no defects affect your final production.

What is TestFlight?

TestFlight is an online tool that allows you to install and exam mobile apps "over-the-air." Historically, app developers tested their projects on actual devices that had to be connected to the development machine using a wire to get a new build. Over-the-air allows developers to distribute their latest builds to testers without the need to connect to the phones physically. Because of this, new builds tin can effectively exist sent to testers in whatsoever part of the globe.

Who should utilise information technology?

TestFlight is perfect for pocket-size businesses that don't have access to a large in-house testing team. And since it's free, it allows for more businesses other than merely revenue-generating companies to use it.

But information technology tin can also be good for enterprise companies with remote testers. The admission and ease of distribution to up to 10,000 external users and the ability to gain their feedback is extremely useful to companies of all sizes.

When was TestFlight released?

On December 23, 2010, TestFlight was founded past Benjamin Satterfield and Trystan Kosmynka. At the time of its initial release, TestFlight was a single platform designed with the intention of testing mobile apps for both Android and iOS devices.

In 2012, TestFlight was acquired by Burstly, which raised a considerable amount of uppercase from venture capital firms in order to develop further features and launch TestFlight Alive (a now discontinued service providing the user with real-time analytics and date metrics).

In February 2014, Apple acquired Burstly. By March of that year, they terminated support for Android devices.

How has TestFlight changed since being acquired?

Today, TestFlight is one of the many options for y'all to use to test your iOS app. Although at that place are alternative systems, a few of these still employ TestFlight to practice their app build distribution, especially since the limit for external testers was increased to x,000 users. With that number of users, you'll be sure to receive adequate feedback and get enough testing washed to ensure a loftier-quality level of your app.

Currently, you can use TestFlight only for apps developed for Apple devices, as it'due south available only to developers inside the iOS Developer Program.

Once signed upwardly for this service, you can distribute your app builds to internal or external beta testers who tin can provide you with feedback about the app. Along with this service, the TestFlight software development kit also allows developers to receive remote logs and crash reports from testers. Being able to get together information from users when they have experienced an issue can be invaluable, as some defects tin be difficult to reproduce. The data from these crash reports could provide y'all with information to aid y'all track down the event and set it earlier it affects anyone else.

At what stage should yous utilise TestFlight?

Although TestFlight would be bang-up during the earlier phases of development to test your initial builds, you demand to upload a release build in order to apply TestFlight. Using release builds to perform initial testing on isn't typical, because they contain less debug information. In the event of a crash, you won't have sufficient details in order to step through the code, find out what happened, and try to gear up it.

Release builds are created when the programmer is satisfied that the major bugs have been caught and it'southward ready to exist a beta candidate build. This is a close representation of the last version that will become to customers. By and large, the build is stable with few to no crashes. Any problems encountered at this phase usually require only minor tweaks, so release builds are better for beta candidate builds.

You tin can besides utilise TestFlight after release to get alive data virtually your app's performance and feedback from users. Gaining ratings and reviews once an app is alive is challenging, so giving users a style to easily submit feedback may help gainsay this effect.

What are the benefits and drawbacks of TestFlight?

While the history behind the product's development gives you an idea of its features, there are many reasons why you may, or may non, want to choose TestFlight for your testing phase.

Benefits

Wide range of users

Being able to distribute your app to upwardly to 10,000 external users over-the-air gives you the opportunity to become feedback for your app from a large number of users that you wouldn't have previously been able to reach.

Having a beta testing group at this maximum amount is almost common with game companies, as they have prospective users registering ahead of time to test the latest versions of a game iteration.

For normal apps, this number of testers is very large. I would typically await a maximum of a couple hundred beta testers. Because remember, the more than testers yous have, the more than test results you have to analyze and feedback you'll need to review.

Keeping the number of beta testers to something sensible is recommended, no affair what maximum limit TestFlight provides.

Testing on multiple apps at once

You can examination up to 100 apps at once with either internal or external users. You lot can also upload different iOS app builds—watchOS apps, tvOS apps, and iMessage apps—at the aforementioned fourth dimension.

Internal users

Up to 25 members assigned to your team in iTunes Connect can besides test your app on up to 30 devices.

Unlike external testers who will take access only to the build that their assigned link points to, internal testers will take access to all builds of your app. If you take multiple versions of your app—for example, a free and paid-for version—the testers could accept access to each build of these different versions so you lot can get one person to test multiple apps.

Quick distribution

The tool allows you to chop-chop distribute your app to a specific set up of beta testers over-the-air immediately. You may choose to build different versions to perform A/B testing of your app with your testers. Existence able to ship a specific build to a number of users at once will help you gain more than results faster.

Easily attainable

TestFlight is integrated within the Apple Programmer Dashboard that you lot demand to use in order to distribute your app within the App Shop. You lot but need to switch tabs to gain admission; no divide login is required.

Drawbacks

iOS merely

If you're developing a cross-platform tool, this will allow y'all to test and receive feedback hands only on your iOS build. Y'all'll accept to do additional work if you want to test the Android build.

Extra review needed to distribute via TestFlight

Apps that use TestFlight will require a Beta App Review and must comply with the full App Shop Review Guidelines earlier testing tin begin.

This is because your app is effectively going out to a select group of the public, then the Apple team wants to ensure that the build that is distributed is of the aforementioned quality as the current releases in the App Store.

Just like with the normal app submission process, if your app has significant changes between versions, you're required to resubmit it for review. This volition add actress fourth dimension to the last phases of your app'due south development earlier it reaches the public.

Afterwards you have completed beta testing, you will need to submit your app for review through the usual iTunes Connect screens.

Limited fourth dimension for beta testing

Submitted builds are accessible from TestFlight for but ninety days afterward invitations to the testers have been sent. The app will finish writing after these 90 days, then you'll have to either update your beta submission or get all of your testing completed within those xc days. This restriction doesn't impact your internal testers, only those external to the project.

Restricted to specific builds

Only release builds that are signed with the correct provisioning contour and distribution certificate are allowed to be uploaded for beta review. So the build needs to be signed appropriately in club for information technology to exist congenital and accustomed.

Only for devices running iOS viii and higher up

A new iOS version is released every year, simply non anybody upgrades and not everyone can upgrade, because Apple chooses to drop support for "onetime" versions of iOS hardware within near three years. This does slightly limit the achieve to your audience, as you have no idea what devices they are using and whether their devices support iOS eight.

No application programming interface for continuous integration/continuous deployment

Unless yous're using tools like Fastlane, the upload procedure into iTunes Connect has to be carried out manually. So this volition slightly dull your progress during testing.

Perhaps Apple tree will create an auto-upload feature within future versions of Xcode only for at present, you'll either have y'all learn to use another tool or spend the fourth dimension doing this manually.

Is TestFlight for you?

Testing your app is a key step in the process of developing one. Without testing, y'all're blindly throwing your creation into the wild with no assurance that it will even piece of work for your potential customers. TestFlight is a robust tool for iOS testing that'll help you lot manage your beta testing stage finer and go it out to potentially thousands of users.

I can completely empathise the excitement to develop your thought into something tangible, but you lot must go on in mind that the goal is to create a nifty app, not simply to distribute anything that resembles your idea into the app stores.

To practise this well, you need to retrieve that integrating thorough testing (even if you're a team of one) into your evolution is essential for edifice a robust product and successful projection. And gaining feedback from beta testers via TestFlight before your product is opened up to anybody could reveal some cardinal insights.

This testing could change some big features and could perhaps put your app on the course to condign extraordinary. Then while there are several drawbacks to using TestFlight, I think the positives ultimately outweigh the negatives and make it worth considering TestFlight as a resource for beta testing your next app.

Disclaimer: All views and opinions expressed in this post are those of the author based on his/her personal experience, and have non been endorsed, sponsored, or otherwise compensated by the companies or products mentioned therein.

cramerconalothe.blogspot.com

Source: https://simpleprogrammer.com/testing-app-testflight/

Share this post