Automation is sometimes done as an afterthought, this usually leads to failure.
Maintaining The automation suite can be tough and a strong infrastructure can help with that.
But, even when there is an automation infrastructure, people are still having hard time maintaining it and running it with confidence and trust.

This talk is about how looking at the automation as proper code and testing the automation framework can help us to solve these problems, when we should do this, how much it is actually worth to invest in, and how we can start doing it.

When we speak about Android automation, the first thing that comes to mind is Appium, however, what if Appium doesn't serve all your Android automation needs, at least not in the most efficient way?

When I was asked to create a test automation framework for our android service (no GUI), I needed to choose the right tool for the mission. After several weeks of researching many options (both commercial and open source). I realized that ADB is my best call because of the following reasons:
• ADB provides a faster to run solution for controlling an android device
• ADB is in a lower level of Android OS therefore it's more flexible
• ADB is going through less code components (like appium client, appium server etc..) and as a result is more reliable

In this tutorial I will share my journey towards deciding to use Android Debug Bridge when it comes to non-gui android application and how I have implemented my choice.
After this tutorial, you will have a better understanding of what is ADB, how it works, and how you can start and apply automation for the Low-Level layer of Android OS with ADB and Python.