iOS apps are well known for their extremely high quality in terms of performance and user experience. Reaching this level of quality needs a lot of testing, but how much is enough? What are the steps to take? How much time will it cost?
We dove into the Apple developer documentation to let them answer this question for you. Here’s what you need to do before starting to test your iOS apps (tldr: skip ahead!):
You should plan for rigorously testing the app on a variety of devices and iOS versions. It’s not sufficient to test the app using only iOS Simulator and a device provisioned for development. A simulator doesn’t run all threads that run on devices, and launching apps on devices using Xcode disables some of the watchdog timers. At a minimum, test the app on all the devices you have available. Ideally, test the app on all the devices and iOS versions you intend to support. For example, if you have a game that’s intended to run only on iPhone and iPod touch, test it on those devices and not on iPad.
To test your app on a variety of devices and iOS versions, create a special distribution provisioning profile, called an ad hoc provisioning profile, and send it, along with the app, to testers. An ad hoc provisioning profile doesn’t require that testers be enrolled in an Apple Developer Program, be added to your team, create signing certificates, or use Xcode to run your app. Instead, app testers simply install the app and the ad hoc provisioning profile on their device to launch the app. You can then collect and analyze crash reports or logs from these testers to resolve problems before you ship your app.
Testing your app consists of these tasks:
- Configure your app for distribution.
- Test your app locally.
- Register all the testing unit device IDs.
- Create an ad hoc provisioning profile.
- Create an iOS App Store Package.
- Install the ad hoc provisioning profile and app on test devices.
- Send crash reports to developers.
And that’s just the start. It can be pretty hectic and consumes a lot of time and effort.
This is where Instabug comes into play. The service that we offer is based on personal frustration from all of these steps needed to start iOS application testing. All developers need to do is integrate our SDK with just one line of code to load the superpowers of our in-app feedback services. Your testers deliver feedback to you just by shaking the device, writing a comment, and attaching a screenshot of the app that can be annotated for further illustration.
iOS developers can log on to our organized dashboard to review all of the feedback received from any number of testers. Every piece of feedback displays the user’s comment, screenshot, and a hell of a lot of useful information about the app and device itself at the moment of sending to make it easy for developers to trace bugs and understand the possible vulnerabilities of their apps. Some of the data provided include memory, storage, device type, iOS version, app version, location, carrier, WiFi, console logs, network logs, repro steps, and more.
- What to ask your beta testers to get better feedback
- Comparison of the top beta app distribution tools
- What beta test legal agreements do you need for your app?
- Instabug blog category: Beta testing