Written by Fred Beringer
Because yesterday was a very special day for TouchTest enthusiasts, we’ve packed your preferred automation production with some amazing NEW capabilities!
Clip editor usability enhancements
We want developers and testers to spend time designing tests, not building them. TouchTest provides a 100% visual environment for fast test creation, and with this new version, accelerates the creation process that no other product will, or can match.
– Redesign of the clip editor to make the information for each action more visible, which makes testing even more readable.
– Outputs, validation and waits can be added easily from each action within the clip editor.
– Accelerate the test building phase and facilitate the collaboration between developers and testers working on the same tests.
Store all locators in a Clip when recording
Mobile app development is very dynamic and traditional automation products struggle with the fast pace of change, because most of them still rely on OCR, which is very fragile. During recording, within a wait or validation and replay, TouchTest has access to all the UI Elements, locators and objects of the mobile application. But because of implementation changes, a good choice of a locator for a particular test might not be the best one for the next iteration of the app and you might want to change it. Using TouchTest you can now:
– Store all locators available for a given UI elements in the clip during recording.
– No need to re-record a clip when implementation requires a change of locator. Pick a different and better one and go build new tests!
HP Quality Center Integration
Many of Enterprise customers will leverage HP Quality Center (QC) to manage their test cases, test campaigns and reports. Our customers were asking to be able to execute TouchTest tests directly from QC. Their dream comes true today with this integration.
– Results of this composition will be seamlessly integrated in QC reports along with other tests you might run (including manual testing).
– Provides a central place where you can assess the quality of your mobile application.
Jenkins Plugin Update
One of our goals is to compress the build-test-feedback process to a minimum. We want to provide developers a continuous feedback loop so they can assess the quality of their code as soon as they’re done writing it. Traditionally, this feedback is given to them within days by traditional testing organization using outdated products. Today, we want to give them this feedback in minutes while extending the scope of their tests.
The second version of our plugin makes it easier for them to setup this feedback loop and adds new functionalities to build a more robust regression test environment.
– Ability to play a composition, make the App Touch testable automatically, Install App on device and capture screenshots.
– Reboot iOS devices
– This is a testing best practice that allows the tester to run a set of tests under a “clean” state. After a while, a mobile device can become bloated and unstable. Being able to automatically reboot devices reduce the number of false-negatives and developers can spend time fixing real problems. This capability is unique on the market today for iOS (This capability comes free on Android)
– Wake up iOS device
– This functionality can be used to make the test environment more robust by waking up any iOS devices and putting them in a “ready-to-test” state. A more robust test environment allows developers and testers to focus on more important activities i.e. Building new tests!
Upload and download mobile apps binaries (IPAs and APKs)
Collaboration and sharing is key in any agile environment. Being able to access the binaries of the mobile apps under tests from within the TouchTest server will help the team struggling to understand which version of the app they should install/test.
– Provides a central place to find apps to be tested
– Avoid reporting wrong information because you’re testing the wrong version of the app
– Increase the reliability of your test environment. Reliable test environment = Efficient overall test process
The mobile test automation effort spans across multiple teams and multiple test environments. Developers and testers might need access to different environment for different purposes: A set of devices might be dedicated to daily builds, others to weekly test campaigns, while some others might be needed for mobile performance tests. A stable, healthy, reliable, and secure test environment is critical in mobile test automation.
With the introduction of device clouds, you can:
– Segregate devices by activities/users and end up with dedicated and stable test environments
– Create Access rules and user permissions and increase the security of your test environment
About the Author
Brad is a cloud-testing pioneer who joined SOASTA in December 2008. His former roles as head of test and monitoring products at Compuware, Mercury Interactive and Borland prepared him well to disrupt the skeptical and established software quality market with updated approaches and technologies for continuous web and mobile testing.