TouchTest Implementation Methodology
TouchTest delivers revolutionary functional mobile app testing automation for multi-touch, gesture-based mobile applications. The data of each touch and gesture precisely captured on a real device can be played back with validations simultaneously on real devices in a public or private mobile device cloud.
TouchTest can operate stand-alone or as a component of your Continuous Integration process, kicking off automated mobile functional testing with the check-in of each new build.
Smartphones and tablets are getting smarter. It’s time there was a mobile app testing solution as intelligent—if not more so. TouchTest is that solution. Conventional mobile app testing tools that use emulation and optical recognition, and that require coding, are far too slow and imprecise for today’s rapid development cycles and complex apps. TouchTest is anything but conventional. It’s revolutionary.
- Capture and playback of all continuous touch gestures precisely (pan, pinch, zoom, scroll, etc.) on iPhones, iPads, iPods and Android mobile devices
- Replace brittle optical recognition testing approaches with touch-based UI testing that allow validations based on variable values and internal app state changes
- Control of test devices via IP address, eliminating the need for tethering, jailbreaking, or contracting with expensive third-party services
- Support affordable testing with real devices in your lab or across the globe
Now, using the SOASTA Platform, developers can integrate performance testing across the mobile application lifecycle. Performance metrics are available during functional testing to catch performance issues early, and functional testing can be integrated with performance testing later to measure the impact of load on user experience. Everyone is looking for a smarter way to test mobile apps. Check out the testing solution that’s infinitely more intelligent.
Real Device Testing
Testing real mobile app user experiences requires testing real gestures and real data on real devices.
Reliable mobile app testing will capture the user experience with record and play back of every gesture and action with precise velocity, movement and orientation, every time.
Faster Mobile Testing
Create and execute tests in minutes and hours instead of days and weeks.
TouchTest customers have reduced mobile app testing test cycles from four weeks to overnight.
Overnight regression testing requires rock solid automation. Kick off mobile app testing with the check-in of every new build. Multi-device, multi-test, lights out regression testing.
The graphic below illustrates the elements of the TouchTest Methodology, which leverages existing best practices to extend traditional approaches to automated functional testing and address the new opportunities and challenges presented by automated mobile device testing.
The following is a description of each pillar and step in this iterative methodology (shown above). The fundamental approach from a business strategy standpoint is to assess the current people, processes and tools used by an organization and map those to the SOASTA methodology.
There are a number of methodology assets associated with each pillar of the methodology available to customers. These assets include videos, tips, and best practices documents around test creation, device management, mobile device test lab construction, continuous integration setup, and more.
A clear and generally accepted strategy is core to the TouchTest methodology. The broader quality and development teams need to understand and buy-in to the overall test automation program. All stakeholders should have a voice in the overall strategy and stand to benefit from its implementation.
Committing to standards and principles of automation will help ensure that all stakeholders in the mobile application test automation program can be invested in the results.
|Mobile Testing Across the Product Lifecycle||This blog posts goes into detail on the importance of continously testing your mobile application throughout it's entire lifecycle.|
|Know Your User||If you don’t understand who your users are and how they use your site, then you’re missing out on creating truly meaningful tests. That’s because a good test plan is about much more than software requirements or functional specs. It starts with a thorough, comprehensive understanding of the user.|
|Know Your Application||How do people exactly use your application? Knowing this will help you design functional tests to validate your user experience.|
|The 7 Steps to Pragmatic Mobile Testing||While traditional software testing focuses on validating, verifying, and measuring performance, today's development teams must also address user experience.|
|Top 5 Common Mistakes Testers Make with Test Automation||This special webinar will describe the TOP 5 mistakes we see as companies adopt Mobile Test Automation.|
|What Happens if I Don't Test my App?||Your masterful mobile app has suddenly become glitchy and unresponsive. Now what?|
|Importance of Mobile Test Labs||Deliver Continuous Quality with expertise, automation, and real devices.|
After establishing the principles and standards that matter to the business, successful mobile functional test automation programs identify specific goals and establish the means to reach those goals.
|Mobile App Testing Checklist||The following video will go into detail on the Mobile App Testing Checklist.|
In order to implement a test automation strategy, it is critical to understand the people and processes that need to be in place. This is the link between the strategy and execution. In some cases it is one or two people who do everything and the processes are rather simple. In other cases, such as the complete overhaul of a mobile application, there will be multiple people for many of the responsibilities and a comprehensive test plan that is part of a much larger process.
The engagement profile is highly dependent on the size of the company and the complexity and length of testing for the mobile application. There are a number of responsibilities, and the extent to which we take any of them on is dependent on the sophistication of the client. Most commonly, there will be multiple people involved in executing discrete tasks, such as scripting, test execution, and test analysis and reporting. For some customers, SOASTA will fill many of these roles.
|Roles and Responsibilities||Specifying specific user's roles in the testing plan is key to positive results.|
|User Permissions||Before scripting has begun, it's important to understand the different permissions that can be granted to team members.|
Once we've established and documented the strategy for testing, as well as identified the participants and their roles, we're ready to start scripting. Depending on the test requirements and complexity, the execution phase may be compressed or extended. Many of the assets used with this methodology are designed to enable rapid testing in response to unexpected issues. In those cases, the established process may not be followed and instead the focus will be on identifying the scenario, the goals of the test, and quick execution.
Because the creation of robust and powerful test clips is crucially important, it's important to follow the guidelines below while creating your new test clips/compositions.
|Introduction to TouchTest Tutorials||The following link will guide you through all of the basic introduction documentation with TouchTest.|
|Location Strategies||The following document will go into detail on the many locators that can be used within TouchTest when scripting clips.|
|Best Practices for Test Clip Scripting||The following checklist will help guide you when creating the overall test script that completes a user story.|
For tests to be valuable to the organization, it's important to look through the following documents and learn best practices for Test Composition playback and creation.
|TouchTest Device Support||The following link will give you the latest information on the devices currently supported by TouchTest.|
|Device Clouds Abilities||The following video will show you how to create and use Device Clouds, the ability to divide devices into specific groups for testing.|
|TouchTest Suite Dashboard||This video will describe the newest feature, TouchTest Suite Dashboard and the abilities it adds to your reporting needs.|
A key component of this methodology is the ability to assess test results and mobile application performance in real-time. This offers the ability to identify and potentially remediate issues during later test executions.
|How to Increase Test Clip Coverage?||The following document will go into detail on what areas of your application should be covered with your current tests.|
Once we have created our baseline of clips and compositions, the final piece of test automation is to integrate our workload into your current CI setup.
The following documents will help you run your current Compositions in an automated fashion.
|Continuous Integration Implementation - Bamboo||The following document will go into detail how to integrate TouchTest testing with common CI tools.|
|Mobile Device Lab Configuration||The following document will go into detail how to setup your Device Lab for fully functional mobile automation testing.|
|Principles of Continuous Integration||The following whitepaper will go into detail on the principles and benefits of Continuous Integrationg testing with mobile applications.|
|Continuous Integration Tools||The following white paper introduces key elements of effective continuous integration for mobile development. In order to reap the speed and quality benefits promised by Continuous integration, it’s important to understand and apply these practices.|
A clear and generally accepted strategy is core to the SOASTA TouchTest methodology. The broader quality and development teams need to understand and buy-in to the overall test automation program. All stakeholders should have a voice in the overall strategy and stand to benefit from its implementation.
As mobile devices change daily, so will the ability to automate this testing. Continue to add new scenarios to the overall suite to cover main areas of use. As use cases also disappear, analyze to make sure old scripts are still useful in your test suite.
As developers create new pieces of the application or change previous areas, continue to maintain old clips by using new locator values....