Page 1 of 96
Testing Criteria for Android Applications
version 1.6: November 2014
__________________________________________________
This is the App Quality Alliance (AQuA) Testing Criteria for Android™ applications.
(Android™ is a Trade Mark of Google Inc).
Applications passing the appropriate tests will be deemed by AQuA to be of a high quality
standard and will be eligible for inclusion within the AQuA Quality App Directory
(
www.qualityappdirectory.org)
This is a new test
This test has been amended from version 1.5
(More details of the changes can be found at the end of the document)
Please read the following information - sections 1, 2 and 3 - before looking at the individual
tests in section 4.
The tests should be performed on a device to which a factory reset has been applied prior to
the installation of the application to be tested. This will ensure that there is a known base
with only pre-installed applications and any errors will be attributable to the application under
test.
It is not within the scope of these criteria to be able to test the performance of the application
on devices with multiple applications installed.
If an application uses another application to perform a function (such as the Facebook
application for accessing Facebook details) it should be tested as if the application
performed that function itself. In this way the user experience is tested as a complete end-
to-end solution and the correct use of the other application is tested as well.
The tests within the Testing Criteria (see section 4) have been developed to test different
features of different apps.
Not all tests have to be conducted for every type of app.
This section describes the different types of apps and the tests to be carried out for each
type.
Introduction
Mobile applications are tested for a number of reasons, chief among these are the needs to
protect the customer and the vendor from software which does not work properly or exhibits
malicious behaviour. The variety of applications is huge and is growing daily so there is a
clear need to tailor testing to the level of complexity. To address this we have defined
applications to be either Simple or Complex.
Section 1 Testing notes
Section 2 Different types of apps and their associated tests
