Mobile test automation has come a long way in the past several years. Both Apple and Google have matured their respective frameworks. We have set industry standards in mobile development now that didn't exist just a few years ago. So do we really need to still scale our test execution across many devices/simulators/emulators, OS's, and resolutions our application supports? Doing so also raises the possibility for more points of failure across devices, cloud services, or internal grids.

For example, devices may lose internet connectivity, connection to the host machine/grid, lose power, reboot randomly, connectivity to cloud service may be interrupted, or our machine resources may not be ideal, thus all leading to flakey test behavior. Also, not to name all the possible conditionals we may need to add (and maintain) in our test code to handle these different devices. At the end of the day, all we really want is to know our application and its various UI views function and visually look accurate across the devices, OS's, and resolutions we support.

In this talk, I'll go over where we've come from and the pain points of mobile UI automation, and where we're heading. I will demo some of the new tools available on the market to help us get there.

In today’s agile world the time to market is becoming increasingly shorter. There is a constant desire to release ASAP to keep ahead of the competition and to please users with updated/new features. Because of this, we have less time to fully do manual and exploratory testing of our apps. Especially, when you consider all the combinations of OS's, Locales, Accessibility, Orientations & Resolutions apps support. Running anywhere from 1 to 100's of Appium crawler bots (covering all of those combinations) at once we can discover more issues quickly and efficiently without having to write a line of code.

UI Automation also has its limitations as it only tests for expected results. Crawler bots test the unexpected, by collecting metadata such as logs, app strings, screenshots, memory and reporting back it’s finding for review so we can test all these combinations quickly and more efficiently. In this talk, I will go over the current challenges we face in today's development world, why we need more tools to help us keep pace, and cover how you can build your own Appium crawler.

I've open sourced this tool and is available here for everyone to use: https://github.com/isonic1/Appium-Native-Crawler

In modern times we have many different cloud testing services to choose from. These cloud services are useful and help reduce the burden of building and maintaining your own Selenium Grid environment. However, there are many scenarios in which you need your tests running locally, such you work for a government (or agency) and cannot expose your data to the cloud, or the service costs are too expensive to run all tests on every commit.

This presentation will feature getting started with setting up your own mobile device grid. Running your tests in parallel and distributed, capturing critical report data (logs, screenshots, and video), and leveraging cloud test services (such as SauceLabs). I will also talk about the challenges and lessons I learned along the way.

In the modern era, we have many different cloud testing services to choose from. These cloud services are useful and help reduce the burden of building and maintaining your own Selenium Grid environment. However, there are many scenarios in which you need your tests running locally and quickly, such as you work for the government (or agency), you have sensitive software/data you cannot expose to the cloud, or service costs are too expensive for your organization.

This presentation will feature getting started with setting up your own mobile device grid, running your tests in parallel, running in CI (Jenkins), and the lessons I have learned along the way.

At 6Wunderkinder, the maker of the Wunderlist app, we have customers whom use our app on many different platforms. It's imperative that our client apps each work perfectly together, and with our server in complete harmony. When unit and functional tests aren't enough, full end-to-end integration tests are needed so we've harnessed the awesome power of Selenium and Appium to accomplish this.