What to do when your tests fail? Read on...

Functional automation is known to be flaky. A test passes sometimes & fail the other times. The failure can be attributed to multiple factors. We need to find out the root cause & then work towards fixing it for increasing automation tests reliability.

In this talk, we will not only be discussing causes that lead to a test failure, but we will also talk about prevention, early detection & fixing these failures for good.

We will discuss some common test failure causes such as locator changes, browser compatibility issues, coding bloopers etc

You will get to know how you can get alerted early about any test failures. We will be discussing topics such as running tests on under development builds for getting early feedback, triggering slack/SMS/email notifications with failure details for immediate redressal and many others.

You will get to know how to prevent failures by building robust locators, exception handling, making use of APIs for test data setup, building atomic tests, making use of waits, retrying your failed tests, rebuilding your Jenkins jobs automatically based upon a failure percentage threshold & so on.

At the end of this talk, you will be confident on how to deal with your failing tests!!

"Buggy App! Why don't you guys hire some good QA. Your app sucks."

How many of you have written a negative play store review? Did you get a response back? In how much time? Was your query resolved?

How would you like if you get a quick response to your comment (say within 15 mins). Your query is then tracked & you are provided a quick resolution. It would be fabulous. Right? Absolutely!

By using some Google & JIRA API's we have automated logging of these reviews into JIRA. For each negative review a JIRA ticket is created with all the details such as Author's Comment, Name, Star rating, App version, Link to original review & Device details such as model number, manufacturer, OS version & RAM. These details help in analyzing the issue at hand.

These reviews are then assigned to the concerned department who can take action on them & provide a resolution by corroborating the review details with internal system logs, verifying app functionality/crashes on that particular device type & reproducing the use case.

These reviews are also attributed to a Review Category by the support team which help us find out areas of concern or improvements for the app. We also try & see if the issue has been reported through other sources as well such as in-app feedback channels/issues reported through mails/call to determine if the problem mentioned in the review is specific to a user or is being faced by other users too. All of this helps us in providing a quick resolution to the user.

In this talk you will get to know all about how to build an ecosystem for app reviews by Reporting, Tracking & Analyzing them.

As a bonus for being a terrific audience, You will get to know about how you can reply to the users review on the play store, Automagically!

We will be discussing about an automation framework that is designed to be configurable so that we can choose a subset of devices to run automation on. We can choose to run the tests simultaneously on all selected devices Or in distributed mode using selenium grid. Additionally all of this is integrated with our own device testing farm which we can use for manual testing as well as for executing Appium tests

We have used STF (https://openstf.io/) for setting up the device farm and have integrated it with our automation setup such that it is seamless to work on. Appium servers are started at runtime according to the requirement. Even the grid setup is dynamically done based on the selected mobile devices.

We all love coding. Don't we?

Give us a new challenge & we will spend nights looking for a solution & automating the same.

We are so occupied with coding, exploring new technologies & tools that sometimes we forget to make the best use of our automation. ‘

How consistently do we run our existing code on the under development builds? What is the impact of app code changes on our existing tests? How can we make sure that the app we are getting for QA is of high quality?

In this talk we will discuss about above mentioned points & more!!.

The end result of the talk will hopefully help drive better quality apps & a fully contented YOU!