We ’ ve be talking to mobile test automation for a while now on our blog, but how does test automation fit into the development operation and how can it help with mobile app screen? Let ’ s take a spry look at why companionship are adopting agile development, what challenge feature to be front when testing mobile apps and how automation can help to attain a uninterrupted speech method.

We live in a pretty hectic world where everything is due yesterday and we can ’ t really disconnect from employment. We expect things to be deliver quicker. That is likewise true for IT processes: we ’ ve seen the unharmed development summons displacement from a waterfall model to uninterrupted integration one and even further to a continuous delivery approach.

But why do companies use agile development?

Using agile development means to release product update more frequently, adjust to the changing priorities on the go, while increasing productiveness and the calibre of the product. All of this will also touch directly how and when testers test the package. Here ’ s a graphic from “10th Annual State of Agile Report”.

What are the benefits for the fellowship that implement agile?

There are threemain benefitsthat have dominated for the previous 5 years in the same research:

1. It ’ s easy to manage changing priorities,

2. Increases team productivity

3. And projection visibility

If you use a waterfall development model, you will have to wait for developers to finish writing the code in its entirety before the code can move on to the testers.

With more agile methods like continuous integration or continuous delivery, dev teams and QA team will work at the same time. As soon as developers write a piece of code, fix a lineament or add a characteristic, the quizzer can run the tests to check if everything is still working and that the new part are working right as well. At that point, the developers check the code again or vary something and a new set of tests needs will be run.

Typical agile ontogenesis cycle

Along the lifecycle of a software or app, testing is done oftentimes and after determined codification writing. This way you can progress a functioning app from the very outset.

At different stages of the app maturation, you will receive to control for different things, running a different variety of (automated) tests.

1. The 1st set of tests will be about unit exam and regression tests which are run on a few devices before the build.

2. The second set of test will be run after the chassis. These tests are typically integration tests, stress tests and performance tests and need to be executed on a larger routine of devices because you ’ re about to release your app.

3. The last set of test is run after the release. These tests are a uninterrupted set of exam and are meant for monitoring, back-end connecter and if want, you can also integrate a clangoring analytic puppet like HockeyApp.

   Pro tip: Tools like SUSA can handle this autonomously — upload your app and get results without writing a single test script.

Testing isn ’ t just QA anymore, but it go a piece of development and operations, besides cognize as DevOps. We will have a DevOps-QA team that is responsible for the package, in every degree of its lifecycle.

Everything we have said until now of the development cycle is not really confine to mobile devices. Desktop covering and software have the like development cycle. Mobile development has its own added obstacles that necessitate to be overcome.

Challenges of mobile app testing

Compared to classic software testing, mobile application testing has some specific challenges, starting with manual testing. Manual testing is in fact no longer a sustainable option when it comes to mobile device, especially with Android, since more than 24.000 different devices have be detected until August 2015.

It appear quite impossible to perform manual tests on all those Android devices. Your users would also face long expect time between the releases – execute manual examination means to screen one device at a time, performing the same actions over and over again. It ’ s not alone time consuming, but wearisome as well, leading to mistakes.Apart from the twist fragmentation you can find other character of atomisation:

• Many different OSs

• Many OSs variation

• Device models atomisation

• Wide range of screen-sizes

One early challenge is the hardware itself. Emulators and simulators can not substitute physical device. You won ’ t get real execution stats, because you don ’ t really see what ’ s bechance to the device like: battery drainage, overheating and the app ram due to previously mentioned reasons. You have a few choice here: you can buy the devices yourself or you can support to a cloud service where you can find hundreds of devices, supply both older and newer model.

App quality has a direct impact on the app ’ s success. And who decides how good your app really is? The users are the ones who will gauge your app and they are unforgiving: they get annoyed by even the smallest bug and they will voice out their opinions, particularly the negative unity.58 % of users will read the reexamination of an app before installing it, if there are many negative reassessment, the app just won ’ t be establish. This will leave in a decreased revenue. So why give exploiter a reason to write bad reassessment?

To make sure to release a-nearly-flawless app, you ’ ll motivation to quiz more. Automated prove allows you to perform more tests while cut your testing time.

How can you benefit from mechanisation and what are the challenges?

Nomadic test mechanisation plays a key role in continuous integration and peculiarly in uninterrupted delivery. The more a ontogenesis cycle becomes agile, the more automated tests have to be executed.

In this environment, testing should be one of the well-nigh important chore in the development round and it needs to be done often, alternatively of just the terminal mile before the release, with no clip for further iteration.

When we verbalize about automation at this point, we talk about functional UI test automation, so basically we assure what the exploiter see and touches.

One of the main welfare of test mechanisation is the reach a wider range of device with less testing time, enabling little release round. One other benefit is that you can test as deep as the network link and many edge lawsuit.

The initial investing to implement mobile examination mechanisation in the development cycle and the learning of know-how is something that you ’ ll have to take into consideration, better sooner than later. Your travail will show you a high ROI presently enough.

With automation, you can also scale your essay which is something you can not do with manual testing.

The chief downside is that you can only use test mechanisation for about 80 % of your testing; there are sure things that you have to test manually. Integrated testing, which is a combination of machine-driven and manual testing, will yet save up to 70 % of try time equate to perform only manual testing.

How do I apply nomadic examination automation?

To begin with test mechanization you ’ ll need test scripts that extend your examination cases. The scripts can be written in different scheduling languages using different frameworks. To speed up your testing we suggest using Appium, which is the mobile specific framework infer from Selenium.

It actually is the nearly versatile mobile UI testing framework supporting many client libraries (Python, Java, JavaScript, Ruby on Rails, PHP, C #). The strong suit of Appium is that it is cross-platform and cross-technology: think about experience to publish just one test script and running it on iOS, Android and Firefox OS and it will too work with both aboriginal and intercrossed apps. If you receive to start somewhere, then start with Appium!

Learn more about testing with Appium with thiswebinar “ Automated your tests like a pro ”!

This post was originally a language I held at the conference Softwareforen Leipzig on the 5th of April, 2016. The focuses of the conference were agile development and automated testing.