This is where you'll find all of the PDFs, slides and videos referred to within the site.
All of AQuA’s work is open source, published under the Creative Commons 3.0 Attribution License. This means that AQuA resources are free for you to share or adapt, for any purpose, provided you attribute and give appropriate credit to AQuA.
Released September 2016
Today’s market is full of ideas of Wearables, The Internet of Things, The Quantified Self, Beacons and many other new devices that connect to smartphones to provide solutions
This gives testers an issue in that it complicates the test environment many-fold. The complexity of test paths could be enormous, and obviously impractical. Consequently, how do testers approach this and how does a risk management approach work in this environment?
This paper looks at the best practice to approach testing a system that is made up from a smartphone and one or more connected things.
Released August 2016
Here is the set of Accessibility Testing Criteria for iOS apps. It is intended to be used to check the application’s accessibility for users with impairments in one or more categories of vision, colour perception, hearing, speech, dexterity, cognition of iOS applications.
Released November 2015
The AQuA Testing Criteria can be used informally at any stage of the development process, but it is expected they will be of greatest use as a check immediately before beginning the submission processes for the Windows Store.
Released November 2015
This set of Accessibility Testing Criteria is intended to be used to check the accessibility of an application for users with impairments in one or more categories of vision, colour perception, hearing, speech, dexterity, cognition on a handheld device running Windows.
Released July 16 2015
This set of Accessibility Testing Criteria is intended to be used to check the accessibility of an application for users with limitations in one or more categories of vision, hearing, speech, dexterity and cognition on an Android Device.
The App Quality Alliance (AQuA) Network Performance Testing Criteria were created to be used in conjunction with AT&T’s Application Resource Optimizer tool (ARO). Since then, AT&T has significantly enhanced the capabilities of the tool, including the ability to analyse streaming video usage, and simulate the effect of changing network reception conditions on-the-fly.
Because the new tool’s output is different and more sophisticated, we have temporarily withdrawn the Testing Criteria for rewriting, but in the meantime urge all developers and testers to make use of the new Video Optimizer tool (https://developer.att.com/video-optimizer) without waiting for new testing criteria. Don’t be misled by the name change – it still delivers an extraordinary level of detail on data usage and power efficiency for any app, whether handling video or not, and enables you to easily see if your app is using more of your customers’ data allowance or battery power than it needs to. We recommend it.
Here's a list of the top 10 tests apps usually fail when tested against the AQuA Testing Criteria.
UPDATED with v1.6, November 29 2014 This is the latest version of the AQuA Testing Criteria for Android applications against which Android apps needs to be tested to be eligable for inclusion of their details within the Quality App Directory. Please see full details of the Directory by going to the site at www.qualityappdirectory.org
This new version includes the following changes:
New test: 4.6 Effects of daylight savings time change
New test: 4.7 Effects of timezone change while travelling
Amended test: 12.2 Installation of unwanted features or concealed add-ons
Amended test: 19.1 Misrepresentation of app, developer or publisher
UPDATED with v1.6, November 30 2014 A list of the tests included within the Android Testing Criteria (v1.6 - November 2014). It shows tests for 'simple' and 'complex' apps, and also highlights whether the tests are 'critical' or 'warning-level' tests.
UPDATED: November 30 2014.
This is the second version (1.1 - Nov 2014) of the AQuA Testing Criteria for iOS applications against which iOS apps needs to be tested to be eligable for inclusion of their details within the Quality App Directory. Please see full details of the Directory by going to the site at www.qualityappdirectory.org.
Changes include:
The AQuA Testing Criteria for Java apps contains a common set of tests against which apps must be tested before they can be considered to be eligible for the Java Verified endorsement.
You should not consider distributing your applications if they don't meet this requirement as this set of tests contained within the document will be used by your chosen test house to test your app.
Please download it, read it, do your QA testing against it before submitting your apps via the Submission Portal.
UPDATED with v1.1, November 30 2014 A list of the tests included within the iOS Testing Criteria (v1.1 - November 2014). It shows tests for 'simple' and 'complex' apps, and also highlights whether the tests are 'critical' or 'warning-level' tests.
This is the latest version - 2.3 - June 2013 - of the Best Practice Guidelines for Developing Quality Mobile Applications, updated to include an area on privacy.
The 3 minute video guides you through the Online Testing Criteria Tool. To start using the tool, just create an AQuA Affiliate account via the QAD site (it's all free). We've also added the iOS platform to the tool ...
Updated in October 2015
In this document we look at how the testing of mobile applications helps to achieve quality.
The latest version has been revised and updated in October 2015 to reflect agile trends in development.
UPDATED November 19 2014: Recent PR coverage for AQuA.
AQuA is a not-for profit organisation supported by membership fees and donations.
All of the resources AQuA provides are free. If you find them useful, please support our work by giving a donation via the PayPal button below.
If you would like to go one step further and get involved, please become an AQuA Member here.