Beta testing guidelines for developer

31
BETA TESTING GUIDELINES www.letsnurture.com

Transcript of Beta testing guidelines for developer

Page 1: Beta testing guidelines for developer

BETA TESTING GUIDELINES

www.letsnurture.com

Page 2: Beta testing guidelines for developer

Beta Testing using Test flight

• TestFlight has been integrated into iTunes Connect and is now available as a native iOS application on devices running iOS 8.

www.letsnurture.com

Page 3: Beta testing guidelines for developer

Device Identifiers and Provisioning Profiles

• it's no longer necessary to juggle device identifiers and provisioning profiles. To test an application with TestFlight there's no need to add the devices of your testers and it's no longer necessary to generate a provisioning profile for ad hoc distribution.

www.letsnurture.com

Page 4: Beta testing guidelines for developer

Internal Testers

• Apple makes a distinction between internal and beta testers. Internal testers are members of your development team that have an iTunes Connect account. Internal testers are managed in iTunes Connect and you can have up to twenty five of them per application.

www.letsnurture.com

Page 5: Beta testing guidelines for developer

Beta Testers

• A beta or external tester can be anyone as long as they have an email address to which iTunes Connect can send an invite. You can have up to 1,000 beta testers per application. Every beta tester can have multiple test devices.

www.letsnurture.com

Page 6: Beta testing guidelines for developer

Beta App Review

• Every build you upload for distribution to beta testers needs to go through Apple's review process. Fortunately, this isn't true for internal testing. The moment you upload a build to iTunes Connect, it immediately becomes available to every internal tester.

www.letsnurture.com

Page 7: Beta testing guidelines for developer

Sandbox Accounts

• The moment a tester opens your application, a sandbox account is created for them. This means it's no longer necessary to create test accounts in iTunes Connect. Testing In-App Purchases was never easier.

www.letsnurture.com

Page 8: Beta testing guidelines for developer

TestFlight for iOS

• Apple also released TestFlight for iOS in which testers can download, install, and update test builds. It's a very convenient way to manage test builds and send feedback to the developer of the application.

www.letsnurture.com

Page 9: Beta testing guidelines for developer

Step 2: App ID

• Navigate to Apple's iOS Dev Center and create an App ID for the application. To use TestFlight, we need to create an application in iTunes Connect and that's what the App ID is for.

• I've set the App ID suffix to an explicit App ID, but it should also work with a wildcard App ID.

www.letsnurture.com

Page 10: Beta testing guidelines for developer

Apple's implementation of TestFlight has a number of advantages. You no longer have to create a provisioning profile for ad hoc distribution, which also means that you don't need to specify which devices are allowed to run the test builds.

www.letsnurture.com

Page 11: Beta testing guidelines for developer

Step 3: iTunes Connect

• Sign into iTunes Connect and create a new application. Select the correct App ID from the drop-down menu and set the version number to 1.0.

www.letsnurture.com

Page 12: Beta testing guidelines for developer

Select the correct App ID

www.letsnurture.com

Page 13: Beta testing guidelines for developer

3. Uploading a Test Build

• Uploading a test build is very easy with Xcode 6. Open your project in Xcode, navigate to the target's build settings, and make sure the Code Signing Identity for release builds is set to iOS Developer for Any iOS SDK. The Provisioning Profile for release builds should be set to Automatic. These are the default settings when creating a new project in Xcode 6.

www.letsnurture.com

Page 14: Beta testing guidelines for developer

www.letsnurture.com

Page 15: Beta testing guidelines for developer

• Before we can create an archive an upload it to iTunes Connect, we need to add the required application icons. If we don't, Xcode will complain and refuse to upload the test build to iTunes Connect.

• The default build scheme archives the project with the release configuration and that is exactly what we want. Connect a test device running iOS 8 to your development machine and choose Archive from Xcode's Product menu to create an archive.

www.letsnurture.com

Page 16: Beta testing guidelines for developer

If you didn't run into any issues, Xcode automatically opens the Organizer, showing you the resulting archive. Select it from the list and click Submit on the right.

www.letsnurture.com

Page 17: Beta testing guidelines for developer

When you try to submit the test build to iTunes Connect, Xcode might display a warning similar to the one shown below. It tells you that it couldn't find a provisioning profile that matches your application's configuration. There's a button labeled Try Again in the bottom right. Click it to resolve this issue.

www.letsnurture.com

Page 18: Beta testing guidelines for developer

When you click Submit, Xcode starts uploading the test build to iTunes Connect. It performs a number of validations during this process, such as checking if the test build contains the required application icons.

www.letsnurture.com

Page 19: Beta testing guidelines for developer

If your test build passes the validations, Xcode tells you that you've successfully uploaded the test build to iTunes Connect.

www.letsnurture.com

Page 20: Beta testing guidelines for developer

4. Build Details

• Head back to iTunes Connect and click the Builds tab in the Prerelease section. Your build should now be visible. Click the test build to show the build's metadata. If you click the tab Build Details, you'll see a technical summary of the selected build.

www.letsnurture.com

Page 21: Beta testing guidelines for developer

www.letsnurture.com

Page 22: Beta testing guidelines for developer

Click the tab TestFlight to see the build's metadata. On this page, you can add information for your testers and Apple's review team.

www.letsnurture.com

Page 23: Beta testing guidelines for developer

• The first section shows you when the test build is going to expire. Each test build is active for a maximum of thirty days.

• In the second section, you can add information the tester sees when they install the test build. You can specify what you'd like them to test, add a description of the application, and include an email address to which testers can send their feedback.

• The third section includes information for Apple's review team. Every build you release to external testers needs to pass through Apple's review process.

www.letsnurture.com

Page 24: Beta testing guidelines for developer

5. Adding Testers

•To enable TestFlight for this application, toggle the switch labeled TestFlight Beta Testing on the right.• If you click the tab Internal Testers, you'll see an empty list. To add testers to this list, you need to mark team members as internal testers.

www.letsnurture.com

Page 25: Beta testing guidelines for developer

In iTunes Connect, navigate to Users and Roles and select your profile form the list of users. To mark yourself as an internal tester, toggle the switch labeled Internal Tester on the right. Click Save and navigate back to the list of internal testers of your application.

www.letsnurture.com

Page 26: Beta testing guidelines for developer

As you can see, internal testers need to be invited as testers of a particular application. Select the testers you wish to invite from the list and click Save. The testers you've selected should receive an email, inviting them to test the application.

www.letsnurture.com

Page 27: Beta testing guidelines for developer

Check your email and look for the TestFlight invitation. It looks similar to the one shown in next slide.

6. TestFlight for iOS

www.letsnurture.com

Page 28: Beta testing guidelines for developer

By tapping the Open in TestFlight button you accept the invitation. This opens the TestFlight application, giving you the option to download and install the test build we uploaded to iTunes Connect. Tap Install to install the application on your device.

www.letsnurture.com

Page 29: Beta testing guidelines for developer

The TestFlight application shows you a list of applications you are invited to test, which is very similar to how the web version of TestFlight works. The main difference is that Apple's TestFlight client is native and allows you to download, update, and open applications from within the application.

You'll also notice that a test build is preceded by an orange dot on your device's home screen to indicate it's a test build.

www.letsnurture.com

Page 30: Beta testing guidelines for developer

Become Beta Tester…

www.letsnurture.com

Page 31: Beta testing guidelines for developer

Follow us on https://www.facebook.com/LetsNurture

https://twitter.com/letsnurture

http://www.linkedin.com/company/letsnurture

Mail Us [email protected]

www.letsnurture.com | www.letsnurture.co.uk