At this workshop, you'll learn about advanced concepts in Appium. We will learn how to write a single script for Android, iOS and mobile web apps. Once our tests are established, we will work on framework design and report. We will also have a detailed look at how can we automate various mobile gestures using TouchActions and mobile endpoints in Appium and running distributed tests in parallel on various emulators and simulators.

Mobile Test Automation is increasingly becoming very important. Almost all web applications are responsive these days and it's very important to test how the application works across devices. The same is true with the native application as well. At the same time, the number of devices and the custom OS versions on devices are also vast. This means that it's harder for a tester to manually run the automated tests over a list of devices to get device coverage and quicker results over every feature development.

We came up with a solution of executing tests in distributed or parallel fashion across remote devices from anywhere in the network using Appium Test Distribution. Same framework is officially used by Appium members for Beta testing of Appium.

USP of ATD over other Market Solutions:

• Device Cloud:
  • Setup Devices anywhere within a network, ATD executes remotely without Grid
  • Never worry about device location in network.
• Plug and Play:
  • Connect your android/iOS devices or Emulators/Simulators and just execute tests.
• Multiple TestRunner:
  • TestNG and Cucumber
• Parallel Test Execution:
  • Runs across all connected iOS, Android real devices and Simulators/Emulators
• Test Coverage:
  • Parallel(Run entire suite across all devices, which gives device coverage)
  • Distribute(Run tests across devices to get faster feedback).
• Device Management:
  • Manage devices remotely using Device Manager.
• Reporting:
  • Covers detailed crashes logs from Android and iOS.
  • Appium Servers logs
  • Screenshots on Failures and On Demand Video logs
  • Reporting Trends for multiple builds
• Manual Access to Remote Devices - OpenSTF support

Who loves/uses ATD?

ThoughtWorks, CeX, Jio, TravelStart, M800, Reward Gateway and lot more.

Idea behind this talk is to describe how to create a short lived containers for each test and scale to large Selenium Cluster using Selenoid. What is standard Selenium architecture and why it is not suitable for big clusters, Also states issues in maintaining a large Docker Selenium Grid / Selenium Clusters. In this session we will also be talking about the challenges we faced in using official selenium docker images and how we scaled up regression execution time from 3:3 (3 hours to 3 mins). Followed by a demo of how Selenoid server solves the problem with docker. How it works, how to use inside big Selenium cluster, where else it could be used.

We have come to a place where we run our selenium tests on pipelines every day.
Now are these tests confined to test only the functionality of the application?
No, we can use this tests to do much more. Let's test security with those same tests.

Turn your selenium tests in to Security tests, get security testing in to your CI pipelines just by tweaking a bit of the selenium integration suite. Find and report security issues that exists which can be caught way before paying off for it.
In this Demo we will introduce a framework that will help your selenium tests turn into security tests and run on pipelines.
With ZAP API + selenium and CI pipelines, find security issues on the application see a red or green security pipeline. Not just that fetch the reports and take necessary actions on every build.
The talk covers different ways that ZAP tests the web application for security(automated with selenium tests). We will see what all of them can be integrated with selenium and can make most out the suite.
As an add we will see how your API can be tested for security using ZAP API :)

Tools used:
1. Selenium Web driver framework.
2. ZAP framework integrated with selenium framework.
3. GO (for CI/CD)
4. Maven for building and fetching reports.

While automated functional tests using appium acts as safety net, there is something missing. Often, we find issues like:

“Sign-In button has shifted a bit and user have to scroll down to see it”

“We asked to change background color of screen-X, it got changed for Screen-Y screen as well”

“Why has fonts of this link become so tiny?”

For mobile apps, look and feel of an application is extremely important. With long running projects, any minor refactoring can change your app’s looks. functional testing tools like Appium can not help us in this case.

Most of the clients are not wanting to use any cloud based solutions, reason been cost and security concerns.

Solution was to build a in-house tool which is Nakal

github.com/saikrishna321/nakal_java