Workshop Day

Thu, Jun 13
09:30

    Registration - 30 mins

10:00

Day 1

Fri, Jun 14
09:00

    Registration - 30 mins

09:30
  • Added to My Schedule
    keyboard_arrow_down
    Jonathan Lipps

    Jonathan Lipps - Appium: The Next Generation

    schedule  09:30 - 10:15 AM place Grand Ball Room people 87 Interested

    Appium hit the open source stage almost 7 years ago and has gone through many iterations of development since then. In this talk, we'll look at how Appium continues to grow, and how the Appium devs are working to ensure Appium's relevance for the future.

    The world of testing is rapidly changing. It's not just about functional correctness anymore: UX testing, performance testing, visual testing, and no doubt several other kinds of testing have descended upon us. Tools and methodologies have also proliferated—image analysis, AI, and other new terms give us pause. What will testing even be like in 5 years?

    I don't know the future, but I know that Appium's philosophy and development methodology are well-suited to ensuring Appium adapts to whatever the testing ecosystem becomes, and I'll give examples both of how Appium itself is evolving to take advantage of new technologies, as well as how Appium's own ecosystem is growing (through a proliferation of Appium-related vendors and products). And of course, we'll save a bit of time for something … interesting.

10:20

    Welcome Address - 20 mins

10:40

    Coffee/Tea Break - 20 mins

11:00
12:00
12:45

    LunchBreak - 60 mins

01:45
  • schedule  01:45 - 02:30 PM place Grand Ball Room 1 people 64 Interested

    Experimentation and quick feedback is the key to success of any product, while of course ensuring a good quality product with new and better features is being shipped out at a decent / regular frequency to the users.

    In this session, we will discuss how to enable experimentation, get quick feedback and reduce risk for the product by using a case study of a media / entertainment domain product, used by millions of users across 10+ countries - i.e. - we will discuss Testing Strategy and the Release process an Android & iOS Native app - that will help enable CI & CD.

    To understand these techniques, we will quickly recap the challenges and quirks of testing Native Apps and how that is different than Web / Mobile Web Apps.

    The majority of the discussion will focus on different techniques / practices related to Testing & Releases that can be established to achieve our goals, some of which are listed below:

    • Functional Automation approach - identify and automate user scenarios, across supported regions
    • Testing approach - what to test, when to test, how to test!
    • Manual Sanity before release - and why it was important!
    • Staged roll-outs via Google’s Play Store and Apple’s App Store
    • Extensive monitoring of the release as users come on board, and comparing the key metrics (ex: consumer engagement) with prior releases
    • Understanding Consumer Sentiments (Google’s Play Store / Apple’s App Store review comments, Social Media scans, Issues reported to / by Support, etc.)

  • Added to My Schedule
    keyboard_arrow_down
    Tomer Cohen

    Tomer Cohen - Low-level android automation with adb

    schedule  01:45 - 02:30 PM place Grand Ball Room 2 people 40 Interested

    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.

  • Added to My Schedule
    keyboard_arrow_down
    Gaurav Singh

    Gaurav Singh - How to kill test flake in Appium?

    schedule  01:45 - 02:30 PM place Jupiter people 65 Interested

    Whether you are a beginner learning the ways of writing UI automated tests or an experienced practitioner, you must have faced the below situation:

    You write a test and it works perfectly in your local, happily you promote the tests to your CI environment and surely it passes initially, however after sometime the test starts failing sporadically. This phenomenon is described as Test flakiness and it’s a bummer for any engineer worth his salt. This can cause numerable side effects and doubts into the minds of software teams not trusting UI automation.

    However all hope is not lost. We all know a Tool is only as good as its master.

    In this talk, I will cover the measures or patterns which you can implement to reduce the flakiness in your Appium tests as much as "humanly" possible and increase their speed and reliability.

02:45
03:05

    Coffee Break - 25 mins

03:30
04:30
  • Added to My Schedule
    keyboard_arrow_down
    Pradeep Soundararajan

    Pradeep Soundararajan - Building Tools to Free up Exploratory Testers

    schedule  04:30 - 05:15 PM place Grand Ball Room 1 people 61 Interested

    I have been a functional exploratory tester. I was motivated to move out of exploratory testing and go into automation. Thankfully, someone pulled me aside and told me - I am more suited to be a functional exploratory tester and I am business savvy. I didn't shy away from code. I worked closely with developers, my testing approach involved reading code (didn't write any) and brought in value to developers and to the business. I grew up as a tester being coached by experts, reading blogs from experts and learning that automation will help exploratory testers do more.

    In my wait - I found very little effort that has gone in direction. I partnered with developers to be building some products.

    I failed multiple times but here are my failed attempts

    1. Tool for Social Media Driven Testing for Testers
    2. Tool for mapping the heuristics and oracles to test ideas
    3. A checklist tool for testing mobile apps and scoring on quality for start-ups

    I would like to share
    - The thinking behind building these tools and their value
    - How purely focusing only on automation is taking away the possibility of building tools
    - How I would love the community to start building tools
    - How I can help and how they can help me

  • Added to My Schedule
    keyboard_arrow_down
    Rajdeep

    Rajdeep - There is more in Espresso Driver's Element than you think/ WhiteBox testing using Appium

    schedule  04:30 - 05:15 PM place Grand Ball Room 2 people 58 Interested

    Have you been in a situation when some cases are impossible to test because Appium doesn't have support? Appium is improving continuously and release of espresso-driver is an example of this.
    Espresso driver opens up possibilities of white-box testing using Appium. One of which is the ability to call platform methods on elements via backdoor without modifying Application under test. What it means is, if the Android platform supports some actions or properties on an element, then Appium will support it out of the box.
    For an automation engineer, that's a very powerful addition. I was fortunate enough to work on this feature and would like to showcase what are the various tricky cases where this feature can be applied. There will be real examples shown with a sample android app. I will also introduce one more small bonus feature at the end, about flashing elements on screen ;)

05:30
  • Added to My Schedule
    keyboard_arrow_down
    Dan Cuellar

    Dan Cuellar - Lightning Talks

    schedule  05:30 - 06:15 PM place Grand Ball Room people 93 Interested

    Dan was selected to speak at Selenium Conference 2012 in London about an entirely different topic. As part of his presentation, he showed off iOS Automation using Selenium syntax to demonstrate writing platform-agnostic tests that use separate platform-specific page objects with a common interface. To his surprise, the cool test architecture would take a backseat to the spectacle of iOS tests running like WebDriver tests. Several people suggested that he give a lightning talk later in the conference to explain exactly how it worked.

    On the second day of the conference, Dan stepped up on stage to give the lightning talk. Jason Huggins, co-creator of Selenium, moderated the lightning talks. Dan experienced technical difficulties getting his presentation to load, and Jason nearly had to move on to the next lightning talk. At the last moment, the screen turned on and Dan jumped into his presentation. He explained the details of his implementation and how it worked, begged for contributors, and in five minutes it was over. The crowd applauded politely, and he left the stage.

    If we look at how Appium came into existence, lightning talks are a very important part of this journey. Hence at Appium Conf, we would like to dedicate a full session with all attendees on Lightning talk.

06:15

    Birds of Feather (BoF) - 75 mins

07:30

    Dinner and Networking - 150 mins

Day 2

Sat, Jun 15
09:15

    Registration - 15 mins

09:30
  • Added to My Schedule
    keyboard_arrow_down
    Jason Huggins

    Jason Huggins - Don't Fear the Robot

    schedule  09:30 - 10:15 AM place Grand Ball Room people 95 Interested

    Don’t worry, the Terminator is not coming for you or your job. But you might need a Terminator someday to test your mobile app. Desktop and web development happen in a relatively constrained environment: keyboard and mouse for input, video for output — easy to virtualize and test anywhere, locally, or in the cloud. However, with mobile apps, running tests in a simulator can sometimes be hard or impossible. There are more parts involved (e.g. touchscreen, physical buttons, camera, Bluetooth, WiFi, etc.) and the possible interactions can complicate a team’s ability to automate end-to-end test scenarios (e.g. receiving a call or text, taking a photo, controlling a Bluetooth device, making an NFC payment, etc.). In those hard-to-automate situations, a robotic device that can emulate human interaction can be a good option.

    In this talk, we’ll go into more detail on why teams might want to make their own robotic mechanisms, and how they can do it without “terminating” their budget or schedule.

10:20

    Important Announcements - 20 mins

10:40

    Coffee/Tea Break - 20 mins

11:00
  • schedule  11:00 - 11:45 AM place Grand Ball Room 1 people 73 Interested

    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

  • Added to My Schedule
    keyboard_arrow_down
    Vivek Upreti

    Vivek Upreti / Naresh Jain - Setting up Jenkins CI Pipeline using Appium tests for Android and iOS

    schedule  11:00 - 11:45 AM place Grand Ball Room 2 people 96 Interested

    GUI and functional tests determine if the product is working correctly from an end user perspective. With increasing number of automated GUI tests we would want to automate when and where they are executed. Continuous Integration helps in merging code to a centralised repository frequently and find out issues early in development cycle in order to help push quality upstream.

    In the talk, you will see examples of how you can setup CI system for Android and IOS native/hybrid apps and how to plugin your Appium tests in the pipeline using Jenkins. We will also talk about the challenges we face while setting it up for Android and IOS applications. We will also talk about how to strengthen your CI pipeline via integrating various tests and Static code analysis tools.

    CI Pipeline

  • Added to My Schedule
    keyboard_arrow_down
    Shama Ugale

    Shama Ugale - Testing Conversational AI

    schedule  11:00 - 11:45 AM place Jupiter people 34 Interested

    Chatbots are one of the most widely adopted AI/ML implementations in the business sector. A chatbot is an intelligent machine used to imitate human conversation through text and voice commands. Today bots are widely used as a personal assistant, customer service, HR, sales and marketing to name a few. In short, bots are everywhere and we rely on them to a certain extent, this makes it extremely important to assure the quality of the chatbots and test them thoroughly. They are built using NLU/NLP-Services (Natural language understanding and processing) and are subjected to constant training and improvement which has direct impact on tests. Voice based bots like Siri and Alexa depend on speech recognition technologies. As the chatbots user do not have any barriers and due to the unpredictable user’s behavior it becomes utmost difficult to verify the correctness on the output. In this talk, we will discuss how the chatbots are different as compared to the other applications and the challenges they bring onto the table while verifying their behavior, and focus on the testing strategies and automation testing of the bots.

12:00
  • Added to My Schedule
    keyboard_arrow_down
    Nozomi Ito

    Nozomi Ito - How we use Appium as our product's core library

    schedule  12:00 - 12:45 PM place Grand Ball Room 1 people 49 Interested

    Appium is very useful tool, but that does not mean everyone can use it without any effort.
    Users sometimes need to tweak command parameters, and the version upgrade of Appium or dependent platform sometimes causes problems.
    As the lead developer of a cloud testing service using Appium as its backend, I have been managing these problems with various measures.
    In this session, I introduce especially unique ones of all these measures such as scroll, wait, picker, AI locator, and so on.

  • Added to My Schedule
    keyboard_arrow_down
    Diego Molina

    Diego Molina - Building a Mobile Testing Infrastructure: What I Learned

    schedule  12:00 - 12:45 PM place Grand Ball Room 2 people 97 Interested

    Mobile is everywhere, and everyone wants a piece of it. All companies want to have mobile apps for their products, lots developers want to code mobile apps, and lots testers want to build awesome tests and frameworks for mobile apps…

    But, what about the infrastructure? Does someone want to spend endless days building a test infrastructure for Android and iOS apps? Not so many people have the time and patience to put all the pieces together and make them work like a Swiss watch. It just seems that many people forget that tests also need a solid infrastructure to be reliable.

    In this talk, I will narrate the journey I went through while doing the job that not so many people want, building a mobile testing infrastructure. The attendants will see all the steps taken in the process of planning the system architecture, how all the components were selected, and how they were put together.

    More importantly, I will share the lessons learned and the open source components that are being used in the final solution, and also guidelines on how to scope the needed resources when building your own mobile testing infrastructure.

  • Added to My Schedule
    keyboard_arrow_down
    Louloua Jawadwala

    Louloua Jawadwala / Reiaz Gafar - The Robots are Taking Our Jobs!! (But in a Good Way)

    schedule  12:00 - 12:45 PM place Jupiter people 38 Interested

    Using Javascript, Ruby, Appium, and some off-the-shelf hardware, we have built our own credit card swiping robot; it has opened up a plethora of testing possibilities for our Register app.

    Shopkeep is a point of sale software company. We use Appium for testing our iOS and Android apps. One of the biggest limitations of our automation suite was that we were unable to test our hardware, including the credit card readers our mobile app interfaces with.

    To overcome this limitation, we came up with a solution to create a simple robot and attach it to a web endpoint. Making simple HTTP post requests, our credit card swiping robot can now swipe cards on the credit card reader. After going through certain iterations in the development of this prototype, we are now creating robots for testing chip card insertion, as well as contactless/NFC based transactions.

    This talk will cover the different components that this robot is made up of. We will also look at the challenges we faced and how we integrated this solution to our Appium automation suite. Our talk aims to inspire you to think of what real, physical objects you can test using a similar solution.

12:45

    LunchBreak - 60 mins

01:45
  • Added to My Schedule
    keyboard_arrow_down
    Srinivasan Sekar

    Srinivasan Sekar / Sai Krishna - Native mobile commands in Appium

    schedule  01:45 - 02:30 PM place Grand Ball Room 1 people 74 Interested

    Apple and Google’s test automation framework does not natively support W3C standards for few web driver spec implementations directly for e.g TouchActions interface in XCTest, etc. Although test automation frameworks support a rich set of those functions specific to platforms, Appium does provide ways to directly invoke these functions e.g gestures, biometric handling, etc.

    Many special behaviors and workarounds are made available and achieved only through executing platform-specific native commands of Appium. For instance, there are 100+ issues been reported on date picker or handling picker wheel in the appium organization but it can be achieved quite easily by executing native mobile commands.

    There are so many that testers might not get chance to go through each one of these and get acquainted with all of those. Native mobile commands help to handle much complex use cases like biometric handling, talking to Siri, performance profiling, etc quite easily.

  • schedule  01:45 - 02:30 PM place Grand Ball Room 2 people 93 Interested

    In this high technology times, it is really hard to catch up with everything. Especially for the mobile world when there are thousands of mobile devices with different modification of the Android OS. Most of us who work in the mobile testing industry familiar with Appium framework for a UI automation and also aware of complicate setup and hard maintenance of it. Using Docker in Android UI automation is making our life much easier. Docker-Android is a docker image built to be used for everything related to Android mobile website or application testing. All the tools needed (devices, framework, Android SDK etc.) are packaged in the image. It is free and open source and supports other features such as video recording.

    In this session, we will talk about the advantages and disadvantages of Appium and docker-android will go throw getting started with Docker-Android and run sample tests against it.

  • Added to My Schedule
    keyboard_arrow_down
    Christian Bromann

    Christian Bromann - Appium for Couch Potatoes: An HbbTV Driver

    schedule  01:45 - 02:30 PM place Jupiter people 19 Interested

    Almost 13 years ago we started with Selenium to automate websites. With Appium we generalised that concept on mobile and just recently entered the Windows and Mac space by adding a Windows and Mac OS driver to the Appium family. Let’s continue our StarDriver quest and enter a (not quite) new sphere: the television. Within the last years, a new standard called Hybrid Broadcast Broadband TV (HbbTV) evolved with which the latest generation of Smart TVs has been equipped. This standard allows broadcasters to build web apps for their broadcast channels to provide additional context information to the TV stream or videos on demand.

    The number of HbbTV apps being developed is increasing more and more as the standard gets rolled out to the whole world. By now almost all TV manufacturers support the standard and due to the high number of TVs in the market the fragmentation is extreme. Different TVs run different proprietary rendering engines with a different level of JavaScript support. Until today the only way to test an HbbTV app is by taking the remote control and manually walking through the app, this has to change.

    This talk will introduce a new driver to Appium that allows the running of automated tests based on the Webdriver protocol for HbbTV apps on Smart TVs. It will explain not only how the driver works but also how in general other drivers do their job in the Selenium and Appium world. We will look into the challenges that automating an app for a TV device brings and will talk about how anyone can build a driver for anything.

02:30

    Coffee Break - 30 mins

03:00
  • Added to My Schedule
    keyboard_arrow_down
    Jonah Stiennon

    Jonah Stiennon - All Desired Capabilities

    schedule  03:00 - 04:30 PM place Grand Ball Room 1 people 124 Interested

    Appium has so many desired capabilities! How many exactly? Let's count!

    Join Appium contributor Jonah Stiennon as he iterates through every desired capability supported by Appium.

    Many special behaviors and specific workarounds are made available only through desired capabilities. Often the key to selecting an element reliably, launching an app, or avoiding a timeout, is picking the right set of desired capabilities. There's so many that testers don't get the chance to sit down and become acquainted with them all.

    There's too many to easily memorize and documentation can be sparse. Jonah will introduce novel ways to classify, visualize, and organize all of the desired capabilities, making it easier to find ones which can be useful.

  • Added to My Schedule
    keyboard_arrow_down
    Kazuaki Matsuo

    Kazuaki Matsuo - Uncovering breaking changes behind UI on mobile applications

    schedule  03:00 - 03:45 PM place Grand Ball Room 2 people 50 Interested

    It is essential to track user logs correctly to improve and develop your own web/mobile services continuously. For instance, how users flow on your applications to evaluate if they work expectedly or not.

    Meanwhile, mobile application trends have been changed quickly such as architectural things or UI related one. Developers continue to add, refactor or rewrite their applications frequently. They also need to release them frequently, 2-week release for instance. Their business also changes quickly. A number of developers working for one application also has been increasing.

    As a result, it is quite difficult to catch up with everything. Developers know a part of them. They add, rewrite or refactor codebase they do not know well with exploratory it. Functionalities related to UI are easy to understand. But, it is difficult to uncover what happens in the backend such as what kind of logs the app sends to servers.

    In Android case, if one application sends a log to a server on a fragment's onCreate. But the fragment can use in another view. If a developer does not know what the log means, he/she might re-use the fragment in another view if he/she think they can re-use it. It can break activity logs collecting on the server side. How to maintain logs is also an interesting topic though.

    In general, we notice the breaking after releasing the app since we can easy to observe the number statistically. But, it means we can not use the data to evaluate our business correctly until we fix it and re-release it.

    In this talk, I would like to show an example of how I had been implemented to uncover the above thing following some scenarios based on my experience. It might be an example what we already can automate in the mobile world.

    This topic is similar to monitor CPU/Memory/network thing. This story is based on my experience I had been worked for a couple of years.

  • Added to My Schedule
    keyboard_arrow_down
    Dawid Pacia

    Dawid Pacia - Mobile & IoT integration testing - "Mission Impossible" or "A last hope"?

    schedule  03:00 - 03:45 PM place Jupiter people 48 Interested

    It is predicted that till 2025 there will be over 75 billion devices spewing 180 zettabytes of data and generating up to 6 trillion dollars. That enormous increase force companies to introduce a continuous approach to deliver the product as fast as possible and be able to compete on the market.


    The main question is how to test application for end user among so much hardware equipment and ecosystems combining HW, FW, mobile devices and complex backend architecture? Considering all factors and possible obstacles is it for companies a real “A New Hope” for companies or just simply “Mission Impossible”?


    I will take the participants on a journey to the IoT world. It will be a talk about the challenges that any tester will face at some point. I will present the dangers, risks and snares but also good practices and practical approach to mobile E2E test automation for the IoT solutions in CI approach.


    Technical examples will be presented using Python languages and supported by physical devices (mobile phones and IoT equipment).

04:00
05:00
05:45

    Closing Talk - 15 mins