Beta testing: how developers test applications on Android and iOS
Very few know what app beta testing during the development of digital products is really about. Everybody knows it is there but very few people pay enough attention to know what it is exactly and how it is done; albeit this is the last step for any application in any of the app stores to actually work.
Both Google Play (Android) and Apple Store (iOS) have their own app testing processes. Developers are aware of these procedures but end users know very little about them. At Google, they have alpha and beta app testing; at Apple, developers can use the TestFlight beta testing system. In the latter case, testing applies to iOS applications, apps for the Apple smartphone and its operating system, watchOS, and apps for tvOS.
Alpha and beta testing at Google Play
Within the Google Play Developer Console, app creators can choose groups of beta testers that will test their products and any subsequent versions which are uploaded to the console. Naturally, this is not an immediate process. And there are some conditions:
· To participate in beta testing users only need a Gmail or Google Apps email account. This is important because it makes life a lot easier for developers.
·App creators don’t have to upload a production APK file (Application Package File) to be able to publish an alpha or beta test on the console.
·When developers upload an alpha or beta test for an application, it will take some time for the link to be available for the group of beta testers. There is no need for excessive rush. The same happens when developers make changes and upload new versions of the same app for testing.
Goggle recommends that developers increase test sizing gradually: start with alpha testing involving a small group of testers and then move to a beta test with a larger group of beta testers. The first group will fine tune the product while the second group will approve it.
Different beta testing models in Google Play
When developers upload the test APK file, they need to choose a beta testing model for the application. The end result is a link they can share with their test group. There are several testing methods in Google Play:
· Closed beta testing model: developers can filter a closed group of beta testers using their Gmail accounts. This method allows them to share the app’s test URL only with the users. The URL is always similar to this one:
Test users can only access the beta-version application if the app’s status is “Published” rather than “Draft” or “Pending Publication”. When they click on the link, testing begins.
· Closed model using Google Plus communities: developers must create a Google Plus community for testing. Users must join the community and opt-in to the test using a link.
· Open beta testing model: this allows developers to choose a group of testers without specifying email addresses or creating Google Plus communities. Developers get a link which they can share in a forum, group email account, web page, etc. This way, they benefit from mass beta testing.
TestFlight, Apple’s beta testing system
Apple likes to say that it has more than 2000beta testers in its app testing system for all its operating systems – within reach of an email account. This is of great help to app developers who need to launch their own products. For the Apple Store, the beta testing system is called TestFlight. This service was launched in Q4 2014 after Apple acquired it.
How does the testing system work? Developers must upload the beta version or subsequent app versions from Xcode. They must add the name and email address of the beta testers for their product to iTunes Connect. In the past, you needed to complete this process for each beta tester individually. However, recently Apple has added the option of creating big groups of test users in TestFlight.
Each app can be tested internally by a group of 25 users; each user can perform the test in 10 different devices. The result is a pretty acceptable test volume. Additionally, developers can invite 2000 users externally and these don’t need to register for the developers program. Each development team may test 100 different apps at the same time.
Test process in TestFlight
Each time a developer invites a user to test the beta version of his/her app, the user receives an email inviting them to join the test group. The message includes a link to a free TestFlight app. Since each user can test the app on up to 10 devices, they can download the app to their iPhone, iPad, iPod Touch or Apple TV and begin testing. The app itself lets users know of any changes and provides instructions.
To install TestFlight, the device’s operating system must be iOS 8 or later.
TestFlight includes a section called “App Details” where every user can submit their opinions about the product (click “Provide Feedback”). Beta testers have up to 60 days to test and give their opinion about the app. Apple’s idea is to make it very easy for testers to be invited to the group, download the app and submit their reviews.
Banco Bilbao Vizcaya Argentaria, S.A. owner of this portal uses cookies and/or similar technologies of its own and third parties for the purposes of personalization, analytics, behavioral advertising or advertising related to your preferences based on a profile prepared from your browsing habits (e.g. pages visited). If you wish to obtain more detailed information, consult our Cookies Policy.
Cookie settings panel
These are the advanced settings for first-party and third-party cookies. Here you can change the parameters that will affect your browsing experience on this website.
Technical Cookies (required)
These cookies are used to give you secure access to areas with personal information and to identify you when you log in.
Name
Owner
Duration
Description
gobp.lang
BBVA
1 month
Language preference
aceptarCookies
BBVA
1 year
Configuration Accepted Cookies
_abck
BBVA
1 year
Helps protect against malicious website attacks
bm_sz
BBVA
4 hours
Helps protect against malicious website attacks
ADRUM_BTs
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BT1
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BTa
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
ADRUM_BT
Salesforce Marketing Cloud
Session
Required for monitoring of the service, inherent to SFMC
xt_0d95e
Salesforce Marketing Cloud
Session
Remember user preferences (if any)
__s9744cdb192d044faa1bf201d29fafd1e
Salesforce Marketing Cloud
Session
Remember user preferences (if any)
wpml_browser_redirect_test
WPML
Session
Text translation in the portal
wp-wpml_current_language
WPML
24 hours
Text translation in the portal
Analytics Cookies
They are used to track the activity or number of visits anonymously. Thanks to them we can constantly improve your browsing experience
Your browsing experience is constantly improving.
With your selection, we cannot offer you a continuously improved browsing experience.
Name
Owner
Duration
Description
AMCV_***
Adobe Analytics
Session
Unique Visitor IDs used in Cloud Marketing solutions
AMCVS_***
Adobe Analytics
2 years
Unique Visitor IDs used in Cloud Marketing solutions
demdex (safari)
Adobe Analytics
180 days
Create and store unique and persistent identifiers
sessionID
Adobe Analytics
Session
Launch's internal cookie used to identify the user
gpv_URL
Adobe Analytics
Session
Adobe Analytics plugin: getPreviousValue Capture the value of a certain variable in the following page view, in this case the prop1
gpv_level1
Adobe Analytics
Session
Cookie used to store the DataLayer levl1 of the previous page.
gpv_pageIntent
Adobe Analytics
Session
Cookie used to store the pageIntent of the previous page.
gpv_pageName
Adobe Analytics
Session
Cookie used to store the pagename of the previous page.
aocs
Adobe Analytics
Session
Cookie that stores the first values collected at the beginning of a process.
TTC
Adobe Analytics
Session
Cookie used to store the time between the App Page Visit event and the App Completed event.
TTCL
Adobe Analytics
Session
Cookie used to store the time between the LogIn event and App Completed.
s_cc
Adobe Analytics
Session
Determine if cookies are active
s_hc
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_ht
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_nr
Adobe Analytics
2 years
Determine the number of user visits
s_ppv
Adobe Analytics
Permanent
Adobe Analytics plugin: getPercentPageViewed Determine what percentage of the page a user views
s_sq
Adobe Analytics
Session
ClickMap/ActivityMap features
s_tp
Adobe Analytics
Session
Cookie used by Adobe for analytical purposes
s_visit
Adobe Analytics
2 years
Cookie used by Adobe to know when a session has been started.
Advertising Cookies
They allow the advertising shown to you to be customized and relevant to you. Thanks to these cookies, you will not see ads that you are not interested in.
The advertising is customized to you and your preferences.
Your choice means you will not see customized ads, only generic ones.
Name
Owner
Duration
Description
OT2
VersaTag
90 days
VersaTag Cookie used to store a user id and the number of user visits.
u2
VersaTag
90 days
VersaTag Cookie where the user ID is stored
TargetingInfo 2
MediaMind
1 year
Cookie that serves to assign a unique random number that generates MediaMind.
Customization Cookies
These cookies are related to general features such as the browser you use.
Your experience and content have been customized.
With your selection, we cannot offer you a continuously improved browsing experience.
Name
Owner
Duration
Description
mbox
Adobe Target
9 days
Cookie used by Adobe Target to test user experience customization.
Looks like you’re browsing from MexicoSpainArgentinaPeruColombiaBelgiumChileUSAFranceHong KongItalyPortugalUnited KingdomTurkeyUruguayVenezuelaAlemania, so let’s show you the custom content for your
location. Change
Select a country
In order to access the private area and corresponding sandbox, select the country of the APIs you want to use.