Documentos de Académico
Documentos de Profesional
Documentos de Cultura
E-guide
In this e-guide
In this e-guide:
p.2
p.6
Page 1 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
p.6
Page 2 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
p.6
Developers don't always remember that a device can lose connectivity -and their app doesn't necessarily behave in a way that makes sense to the
user when that happens. It isn't good for an app to freeze when the device is
set on airplane mode -- but that still happens all too frequently.
There is no substitute for having a separate team (apart from the
development team) test an app on real devices in a real situation before
giving the app to users.
Tell us about AQuA's app testing criteria. How were
these developed?
Wrigley: AQuA has criteria for Java, Android and Apple
iOS apps. We are working on Microsoft criteria as well.
The criteria are designed to catch the majority of
common errors in apps. These criteria have been
developed over time, mostly in response to errors that our
members have found in apps. As we find new trends, such
Page 3 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
p.6
Page 4 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
p.6
apps that are much more attractive to look at, but the teams behind them
may not necessarily have the software engineering skills that the traditional
development teams may have had. As a consequence, they may not have
the testing expertise to look beyond the immediate functional testing that
people tend to do.
The AQuA testing criteria gives developers a cost-effective way of
performing a structured set of tests -- a checklist -- to avoid easily
overlooked errors that otherwise keep causing issues in the apps.
What testing advice do you have for teams building their first mobile
apps?
Wrigley: In the planning of your app, think about the types of tests you need
to do and don't skimp on them. It's always tempting to put in another feature
and miss out on some of the testing, but if that ends up with your app
crashing, that extra feature will not be much compensation.
Next article
Page 5 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
p.6
Mobile testing tools are experiencing a growth spurt. New products and
services emerge nearly every day, and the time and energy needed to
evaluate them may make all the free trials in the world seem not so free. This
article looks at several mobile testing tools, listing their benefits, features
and tradeoffs to help testers and IT managers make smarter investment
decisions.
The first major challenge with mobile testing is the host -- that is, the device
the tests will run on. Unlike a laptop or desktop, where the tests are
developed and run on the same device, automated tests are typically
planned and programmed on a laptop and run on some mobile device that
may be plugged into the laptop and emulated. Or the mobile device might
run somewhere else and be connected to the test driver over the Internet.
Most large testing programs require testing on a handful, if not dozens, of
machines, making physical plug-and-play untenable. These challenges
should receive special attention when reviewing tools.
Page 6 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
p.6
Appium
Appium is a small server written in node.js. Appium allows users to access
their Android or iOS environment where they have the server running.
Since Appium uses the WebDriver framework, it can run tests in any
language that WebDriver supports. Webdriver is a popular Web API that
developers can program in many languages, including Ruby, Python,
JavaScript and many more.
Page 7 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
p.6
On the plus side, Appium is free and based on open source components. On
the downside, that means setup can be a hassle; you have to install open
source prerequisites and make sure the versions are compatible.
Page 8 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
p.6
p.12
Sauce Labs
Sauce Labs offers a mobile testing product based on the Appium
framework. Strictly speaking, Sauce Labs uses the Appium tool to host the
tests, providing the environment for running digital tests. This approach
provides the same benefits of freedom of programming language and dual
(iOS, Android) platform support while removing the need for physical
hardware.
In other words, Sauce Labs uses the Appium framework, but gives testers
the device to run the tests on a virtual mobile device, then bills the device as
a metered service by the CPU hour. This service is built in the same way as
Page 9 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
p.6
other Sauce Lab products, so testers get similar features, such as the
potential to watch videos of tests as they run, or to link those errors
reported in a test to a particular point in the video, making debugging much
easier.
However, unlike the previously mentioned tools, mobile testing supported by
the Sauce Labs platform is not free. The manual subscription plan is $12.00
a month, the individual plan is $49.00 a month and the small team plan is
$149.00 a month. Enterprises should contact Sauce Labs for further pricing
information.
Perfecto Mobile
Perfecto Mobile is not based on WebDriver. It has a native UI based on a
proprietary TCL-based programming language. This approach lets testers
who are not programmers select behaviors from a simple, no-coding
development environment and write expected results in simple English.
Tests designed with these proprietary tools may be more costly to move
away from than tests written with open-source tools.
In addition to its native UI, Perfecto Mobile provides a RESTful API for
integration with other interfaces including WebDriver and JUnit. Like Sauce
Labs, Perfecto Mobile can provide either simulators or cloud-based real
devices to run tests on. Perfecto Mobile recommends running tests on real
Page 10 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
p.6
Driving the user interface with mobile testing tools is massively popular in
the software world, and automation of mobile websites is quickly becoming
common practice. This growth has caused an explosion in companies
creating mobile testing tools. Now that testers have so many tools to choose
from, the choice is more complicated, often made worse by folklore
surrounding test automation and marketing material. Hopefully, this article
provides a starting point for testers' research.
Next article
Page 11 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
p.6
Page 12 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
Testers also can divide the list between releases. Granted, not all features
will be tested in the initial release, but a group can be tested each release
until testing is completed. Create rotating test suites and mix them into your
regression testing executions. Once each has been thoroughly tested, go
back through and mix them at random or by feature and add them to the
regression test along with their matching feature.
p.6
Another logical option is to test them with the feature they control. If the
testing numbers are too high rotate the feature and create small subsets of
test suites that cover a piece of each feature. Switch out testing suites each
regression cycle. Each testing suite contains a portion of every feature so in
this way, full testing occurs over a series of regression testing events but all
features are covered to some extent.
Next Article
Page 13 of 14
E-guide
In this e-guide
App Quality Alliance compiles
mobile testing criteria
p.2
p.6
Page 14 of 14