Why Mobile App Testing?
TouchTest® Mobile, featuring TouchTest™ technology, delivers for the first time, complete functional test automation for continuous multi-touch, gesture-based mobile applications. TouchTest™ technology delivers fast, precision functional testing while increasing the stability of automated tests across releases.
TouchTest controls mobile devices through a lightweight web service called TouchTest™ Agent. Devices can be dedicated to testing in the lab, used as part of an external test, or crowd-sourced as part of a high volume, globally distributed test.
SOASTA TouchTest® provides fast, effective performance, load and functional test automation of any modern Web application, Web service, or mobile application in a lab, staging or production environment using unique visual programming and multi-track user interfaces. The TouchTest platform can utilize both public and private cloud resources to assure any web or mobile application won’t fail under peak user traffic.
The Composition is the test itself as presented in the Composition Editor, and contains one or more Clips arranged on Tracks and governed by user-specified sequence and tempo. The Composition Editor is a player, debugger, and the dashboard where results are analyzed.
The Clip is the basic building block of a test as built in the Clip Editor and has a Target such as a web site, or in the case of TouchTest™, a mobile app. A clip can be thought of as a visual script that is composed of a series of timed or sequenced events, which correspond to gestures performed on the mobile device. It can contain messages, browser or app actions, and scripts, as well as delays and checkpoints—all of which can be organized into containers (i.e. groups, chains, transactions, etc.)—and parameterized as required.
TouchTest clips are recorded directly from the mobile app and added to the Clip as you perform them on the mobile device.
What Does Touch Test Record?
TouchTest™ records the details of actual gestures and events that invoked on the app that is tested. These gestures and events are represented within the Clip Editor as App Actions. Precision recording captures and plays back all continuous touch gestures including pan, pinch, zoom and scroll.
Each gesture you perform on a TouchTest-enabled device is precisely, and automatically, added to the test clip as an App Action.
Like any clip element within TouchTest®, App Actions have inputs and outputs, as well as properties, waits, and validations that can be parameterized. Additionally, an App Action can be added to any containers (e.g. transactions, groups, etc.).
As a general guideline, your test should account for all the factors of the mobile app(s) you want to test, and include one, or, as many viable test cases as it will take to arrive at a good mobile app test case.
Once a test case is recorded a test designer can move quickly to validating captured app actions and other test design issues. Test design also takes into account the following factors:
- The types of app actions to perform: The test designer will consider the types of app actions that make up a test case for the given mobile app. These app actions should then be performed during recording.
- The timing of app actions: In addition to TouchTest’s built-in detection of the duration of gestures, CloudTest® provides an additional set of Waits, which allow the tester to gain control of the pace within a test.
- The validation of tests: Verifying the behavior of a mobile app is another important step in successful testing. After each app action is recorded, the test designer can add as many validations as needed by picking from among built-in Verify commands.
- The number of devices and their locations:Typically, a single test clip defines a single test case that can be run on multiple tracks or devices. However, tests of great complexity can be quickly devised by introducing multiple test cases, multiple devices/repeats—in tandem with geographic location. Complex mobile app tests can be easily built utilizing one or all of these capabilities.