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.

Application Backdoor via Appium

There's a shift towards open-source mobile test automation tools happening today among developers and QAs. Whether it be Appium, Calabash or anything else: all are good, with some major limitations.

While a chosen tool may work well when you first start using it, things can quickly get out of hand with changing business requirements. We started using Calabash at Badoo when there was no Appium. Given the capability of Appium to drive the whole device, we started automation of new apps with Appium. However, we realized a powerful feature was missing in Appium for Android! : The ability to call Application code from automation code like Calabash Backdoors.

As Appium UiAutomator server is based on instrumentation, we modified it such that we could instrument our app under test. This gave us the power to access context of Application under test and invoke public methods of Activity using reflection APIs. We use these methods to setup app state, seed DB OR even enable/disable some client-side A/B tests. This makes our application more testable and our tests more predictable.

This talk is going to be about how I achieved the above solution and benefits of backdoors.

There will be a small demo and code!

still writing relative xpath manually ?

Do you want to save 20-30% time of automation script writing ?

Feeling frustrated while writing unique locators ?

looking for firepath replacement ?

As ReactJS is overpowering AngularJS as the go-to framework for front end development, testers tend to find the best tool which suits all of their needs in the javascript world.

Join this talk to learn about "Why and How to use the Power of NightWatch" as compared to other existing popular automation frameworks in the testing industry today such as Protractor, CasperJS :

• how NightWatch makes test code highly transparent and readable
• how NightWatch adds layer of abstraction separating the HTML selectors from the page objects, thus, enabling reuse and promoting general tidiness in comparison to other testing tools
• how running tests against specific browsers/environments in parallel is relatively easy with NightWatch
• how it solves the problem of tests re-write (say login for use in multiple cases)
• how you can extend/enhance your tests using custom commands, custom assertions and custom reporters
• how you can automate mobile apps integrating NightWatch with Appium

Many good product and project teams try to understand the “whys” when they’re asked to build a new feature. But, how do we know whether our reasons are actually good enough?

Are we tracking customer behaviour and feedback to get more insights into building the “right product”?

Do we have analytics? Are we monitoring issues/crashes and user suggestions? Are we automating these processes?

In this talk, we will share how we did our analysis in order to get better insights for building the right product and adding more value to our customers. We will share our experience, challenges, etc. We will also talk about a small utility (Sentiment Analyser) we developed which helps us to generate meaningful reports from user's feedback on daily basis.

We will also cover how we’ve automated analytics and understanding the sentiments of our customers.

There will be a demo for Analytics Automation and Sentiment Analyser.

In this world of asynchronicity, where it is easy to build applications using single page application frameworks, people struggle at the writing functional tests for such applications.

Understanding this asynchronous nature of newer tools and frameworks needs efforts. In this talk we will talk about our journey from writing test with callback (hell) to using Promises and finally achieving nirvana with the power of async/await in JavaScript.

This is a time travel of asynchronous programming and where does the future lie. The discussion will include:

• Callbacks and their nested nature
• Removing callbacks with Promises
• And migrating to async/await