Agile Testing in Mobile Development Process

New Way of Testing Mobile Apps, Games and Web

Dear Testdroiders,

When it comes to users rating or reviewing your mobile app in app markets, they typically aren’t too shy about problems. The threshold to get in and write some bad feedback about not well-behaving/not-working app is pretty much nonexistent – and quite many users do that. Mobile apps are becoming so crucial part of people’s lives that they will share their love or hate about these. And feedback, even written on motional state, will get in front of hundreds of millions of users. But are those ratings the top thing to focus? Not really, but something else actually matters the most…

The mobile app quality has become crucial for all different players among mobile ecosystem. From indies to middle-size app/game studios and large corporations pushing apps for consumers in various sub-verticals (banks, retail, insurance, travel, and dozen of others) understand what gaining five star feedback for their app means.


We’ve been discussing about the new Agile process that can help organizations producing better mobile apps for users and the infrastructural/architectural aspects that needs to be considered in the development process. To build efficiently and create those features that drive your app usage up and forward, plus provides a great user experience, testing in continuous manner is typically in the epicenter of the process.

First, some facts: Things that get done manually are never agile. Testing the mobile app manually an exception. Humans are error-prone and each and every manual session with your mobile device is different (regardless of what you think or say). Only test script can do that repetitive process the same way, again and again. In addition, manual testing can be the no. 1 factor to slow down your development and the root cause to delay release of your app.



The solution for faster iterations and instant error reporting resulting as a better app quality comes through Agile testing, test automation and efficient use of continuous integration. And not to burden devs too much, they should always focus on developing new features, doing enhancements and – of course – fixing those bugs. The way to identify those bugs varies and in this blog we’ll take a look the Agile testing way in mobile context.

How do you define the success of an app?

Sure, app ratings matter and have a direct impact on installations: the better ratings, the better position in search. That’s the fact we all know when looking for different sort of apps in Google Play and App Store. But the rating isn’t all about search and downloads, but more importantly, it’s about the revenue and how quickly your app can generate that.

“App ratings do count for downloads, and downloads count for revenue generation, and revenue generation counts for your success.”

This equation is missing one important attribute: time. The sooner you get your app in front of users – and as a robust and fully working – the sooner you’ll start generating revenue. Any app’s time-to-market counts not only against competition but also when the revenue starts rolling in. Simply, time-to-market can be improved with integrated development and testing flows.


There are lots of variations in end-user platforms (ie. devices) that your apps should support and ever increasing complexity in apps that need to be tested on those end user devices in every release. In Enterprise apps world, bring your own device policies (BYOD) create the same need for organisations’ internal apps. In large organisations, there are easily 30-50 different devices from tablets to smartphones to be supported and tested with every release. At Enterprises, daily volumes are naturally lower, but value per mobile user is much higher than with consumer facing apps & games.

Continuous Integration, Development, Testing, Quality and Deployment – A comprehensive approach for app quality

The use of automation is already in an epicenter of how developers build their software. Typically companies rely on continuous integration tools (like Jenkins) that bring clarity for both, development and testing. In a nutshell, continuous integration provides a workflow to help managing code and its regressions, and then enabling efficient testing of those builds. With this sort of Agile approach, continuous testing can also happen every time code changes in repository.

In this example, company can entirely focus its efforts on building new features, versions, enhancements, and take care of bug fixing, while testing happens automatically and entirely in managed manner. For example, building a new version of app can take a place every day and then that application gets tested – before the next iterations take place. It’s provide very efficient way to improve the overall app quality, find out and rub out the bugs instantly and not drag those with the app, build by build.



So what gets delivered during these “Professional services”? We strongly believe that effective mobile testing derives from a well-structured and systematic approach, use of some (preferably cross-platform) test automation framework, and the use of real mobile devices, combined all that with seamless integration to agile development process. This type of process gives great visibility on what is actually the quality of app development. This approach also adds some time as you will get instant reports (with logs, screenshots, recorded video of sessions, and results in general) how well the app performs across variety of those real mobile devices.

After the app (APK or IPA) gets built, it can be automatically send for its first test – the smoke test – to see how well it compatibles with those devices. Also, each regression can be tested (regression testing) with the existing test cases/scripts for certain specific function. For example, if app relies on back-end services, this connection can be after each build-in regression testing with automated scripts. In addition, many other aspects can be also automated: localization (testing different languages), different types of performance tests (load, spike, stress and others), connectivity and hermetic testing (isolation of app from network, other services etc.).

This might sound complex but the beauty is that we’ll take care of all those nuances, fine-grained details and larger entities for you. That’s why Testdroid Professional services provide outstanding value to its customers – and enables you to focus on your core competences.

Interested to know more about Professional services? Get In Touch and We’ll Tell You More!

Screen Shot 2015-09-14 at 1.03.48 PM

  • Jared

    Great article on agile testing and how the process works on mobile! Thanks for writing!

  • Nice blog on app testing. Its good for the developer and tester point of views. Following these process will lead to higher quality apps, better user engagement, and stronger app ratings.

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.