Conference Time
Local Time

Appium Lite

Thu, Sep 2
Timezone: Asia/Kolkata (IST)
19:00
  • Added to My Schedule
    keyboard_arrow_down
    Maaret Pyhajarvi

    Maaret Pyhajarvi - Many Hats to Make a Tester

    schedule  07:00 - 07:20 PM IST place Zoom people 172 Interested star_halfRate

    Recent years have moved teams away from having testers to having developers who test. When we accept we can’t automate without exploring and we can’t explore without automating, the split to manual and automation makes little sense. We need to discover new ways of decomposing the testing work to share that in the team. 

    In this effort, we’ve discovered that what we used to expect from one tester, is now split to four developers each with a different emphasis for the team to be successful together. In this talk, we look at how our virtual testing team - a whole team responsible for both developing and testing an application, has split the many hats of testing identifying 15 hats for us to distribute the best way the team sees fit. 

    Who carries the hats of a product historian, on-caller, parafunctionalist or feature shaper in your team, and which of the hats are hard to keep up in your current team composition?

19:30
20:00
20:30

Pre-Conf Workshop Day 1

Wed, Sep 15
09:00

Pre-Conf Workshop Day 2

Thu, Sep 16
09:00

Appium Conf Day 1

Fri, Sep 17
10:00
11:30
  • Added to My Schedule
    keyboard_arrow_down
    Sai Krishna

    Sai Krishna / Srinivasan Sekar - Build your own Appium plugin

    schedule  11:30 AM - 12:15 PM IST place Zoom people 181 Interested star_halfRate

    What if you had to support a custom locator in your project and with Appium 1.0 it was not possible. This would lead us to maintain a fork and make our required changes. Which in turn is an overkill as we have to always keep up with upstream. 

    With Appium 2.0 architecture we can create plugins for our special needs. At this talk, we are going to talk about Appium 2.0 architecture, how to create custom plugins and what other breaking changes we brought in Appium 2.0. 

  • Added to My Schedule
    keyboard_arrow_down
    Gaurav Singh

    Gaurav Singh - Hello Appium! Setting up your First Appium Tests efficiently

    schedule  11:30 AM - 12:15 PM IST place Zoom people 158 Interested star_halfRate

    Despite all the available blogs, tons of tutorials and resources out there

    Getting started with Appium is still really hard. Where should you start when you want to take your first baby steps towards Appium?

    Well, this talk is for the beginners in the crowd, the noobs if you will. However, even if you are an intermediate appium user, a refresher does not really hurt, does it?

    In this tutorial, I’ll help you get setup quickly and efficiently and give you the quick launchpad to get your hands dirty with Appium on both Android and iOS

    We’ll cover:

    • Mind map of the different areas/components to consider when first learning and getting started with Appium
    • All the steps that you need to follow to set up Appium (Current and 2.0 version) efficiently on your machine and run your first Hello world like Appium test on android and iOS.
      • Setup:
        • Setup emulators and real devices
        • Install and setup Appium server
        • Set up your IntelliJ project and Gradle dependencies
        • Setup project structure with page object pattern
      • Setting up driver
        • Setting up desired capabilities and boilerplates to setup driver instance
      • Finding elements
        • How to use Appium Desktop for object identification
      • Writing your first tests
        • Writing your first test on Android
        • Writing your first test on iOS
      • ADB/IDB
        • Understand basics of ADB/IDB
      • Setup reporting
        • Get quick reporting out of the box
    • What could be next logical steps to take

    This entire starter kit code repository (both android and iOS) would be uploaded to GitHub so that you can take this ready made sample and be on your way. 

    I hope you don your Beginner’s hat and join me for this exciting talk and Let’s make Getting started with Appium super easy.

  • Added to My Schedule
    keyboard_arrow_down
    Babu Narayanan Manickam

    Babu Narayanan Manickam / Gajendran Ganesapandian - Building Highly Scalable Appium Infra with Terraform and Kubernetes Cluster

    schedule  11:30 AM - 12:15 PM IST place Zoom people 142 Interested star_halfRate

    Problem Statement

    Our recent customer mobile apps were demanding for increased number of device testing to enable better test coverage. Considering, the availability and cost of real devices, the simulators and emulators were found to be alternates. However, the simulator infrastructures were difficult to build, scale, manage and/or expensive when it is rented on cloud specially while executing in parallel.

    Our Solution

    The initial purpose is to build a manageable appium test environments that can offer multiple device simulators with parallel test options at a minimum affordable cost and with simpler configurations. When minimal viable solution is built, we improved the scalability, performance and made it cloud agnostic.  

    In this talk and demonstration, Gajendran and myself will demonstrate scaled Appium Pods designed using Terraform and K8S Cluster and run several parallel tests in AWS Cloud on 10+ different simulator combinations.

12:30
13:00

    Lunch Break - 60 mins

14:00
15:00
  • Added to My Schedule
    keyboard_arrow_down
    Daniel Paulus

    Daniel Paulus - Execute Appium iOS tests inside Linux containers

    schedule  03:00 - 03:45 PM IST place Zoom people 133 Interested star_halfRate

    Setting up Mac OS X for remote use or as a CI pipeline is never a great experience. Usually we all love using Linux for these purposes, sadly iOS devices don't work on Linux.. or do they? Wouldn't it be cool to just execute Appium servers for iOS devices on Linux machines in Docker containers?  Turns out you can absolutely do that and this talk explains how.

    I have created go-ios (https://github.com/danielpaulus/go-ios) an open source library that allows you to access iOS device functions like:

    • launch XCTests (like WebDriverAgent, an Appium requirement for iOS testing)
    • start and stop apps
    • and many more

    from the command line on both, Mac OS X and Linux. 

    Because we are using unstable, private Apple APIs, I included my reverse engineering tool "dproxy" that you can use to debug future iOS updates or add missing features to go-ios. 

  • Added to My Schedule
    keyboard_arrow_down
    Wim Selles

    Wim Selles - Swiping your way through Appium

    schedule  03:00 - 03:45 PM IST place Zoom people 158 Interested star_halfRate

    Mobile applications are becoming more and more important in our daily lives. From ordering clothes to grocery shopping, the services available via an app are increasing rapidly and users expect a seamless experience. This means that the automation focus is shifting more towards mobile devices. 

    But did you know that there is a huge difference between interacting with a desktop browser and a mobile app? And that difference is just a few tiny hand motions! Because with desktop browser automation we mainly focus on using our mouse, but on devices, we use our fingers to execute all different kinds of gestures, like swipe, scroll, pinch/zoom, and many more. Did you also know that automating mobile gestures is one of the most overlooked features in mobile automation?The most common reason for this could be that we don’t know how to do it, or because it might just be too difficult. 

    During this presentation, we will focus on how to mimic mobile gestures with Appium for Android and iOS. With a sample app we will explore and understand different gestures including how to scroll, swipe, and pinch/zoom and then create cross-platform and cross-device gestures. By the end of this presentation, you’ll learn how to improve the user experience of your mobile applications by adding gestures to your automation scripts.

  • Added to My Schedule
    keyboard_arrow_down
    Ragavan Ambighananthan

    Ragavan Ambighananthan - Why cross browser and device platforms are ripe for disruption?

    schedule  03:00 - 03:45 PM IST place Zoom people 90 Interested star_halfRate

    Goal:

    To scale desktop/mobile web/app test automation in a cost-effective way that would meet the demands of good software development design patterns like Shift Left, at the same time, be cost effective.
     

    Problem Statement:

    Current cross browser/device platforms are not built to handle the real scalability that software development design patterns require, in a cost-efficient way.
     

    Expensive parallel connection limit:

    Most or all cross browser platforms, offers their services based on the number of parallel connections.
     

    Shift Left and Scalability:

    Problem with current approach followed by these platforms is that it is not aligned to software development best practices like Shift Left.
    With Shift Left, automation suite would run for every commit in a branch of a project, the number of tests running at any point in time is significantly high. Again with this being repeated by many teams, within their own CICD pipeline, across an organisation,, the demand for parallel connections increases exponentially. The cost to support this using current cross browser and cross device approach is astronomical.
     

    Restricted Real Device Usage:

    Most cross browser and cross device platforms' primary support are around real device and not emulators or simulators. With real devices, there is restriction on the number of concurrent tests you can run, based on device types and tiers, even though you may have higher parallel connections purchased. This is due to limited number of real devices a platform has and having to share it with 1000s of customers on demand.
     

    Data Center vs Cloud:

    Fourth reason is, most these platforms rely on data centres, instead of Cloud. Hence their ability to dynamically scale desktop/mobile automaton infrastructure is very limited.
     

    Desktop is still king of conversion:

    Fifth, as much as we would like to think that mobile web is matured, conversation rate in mobile is the lowest compared to Desktop/Tablet as per Akamai. It could be due to many reasons, including performance, usability, etc. This also means that, since the conversation is more in desktop,  importance of testing on desktop browsers is still by far more.
     

    In App Browser Testing:

    Sixth, In App Browser is a new trend, where you might have tested your mobile web on different browsers, but it will probably mostly viewed in an In App Browser like Facebook In App Browser (When you open a site in Facebook, it opens it within Facebook's realm instead of on a browser). Even though In App browser uses Chrome or Safari, many users are complaining, that their site is broken when viewed via In App. Companies like Facebook / LinkedIn would like to keep you within their realm so they can track you, hence your mobile web site's experience should also be tested in these In App Browsers. 2018/2019 Facebook In App Browser usage, showed 42% increase as per Akamai.
     
    This means, you have to test your mobile site in In App Browsers as well.
     

    Emerging Country Specific Browser:

    Revenue generation percentage for international eCommerce companies is traditionally very high (more than 50%) from U.S, but this is changing where it is normal for a company's ~50-60%% revenue to come from non-US markets. This is also another reason to look at local browser usage habits.
    Chromium based Cốc Cốc browser is used by 25 million people in Vietnam.
    UC Browser and QQ Browser are number 2 and 3 in China and UC Browser is number 2 in India.
    Yandex is number 3 popular browser in Russian Federation. Just these 4 countries alone has around 2.5 billion people.
     
    These are many of the problems with the current Cross Browser / Device Platforms.
    a) Expensive parallel connections, b) Limited scalability thats not suitable for good SDLC design patterns c) Real device restriction d) Data centre limitation  e) New use cases, increasing scope and frequency of testing  f) New region specific browsers
     

    New Opportunities - Evolution of Technologies

    Now let us look at what has changed in terms of technology that could take us away from the above problems.
     
    a) AWS mac1.metal (Mac Mini computers) - AWS, for the first time, providing scalable Mac minis. Even though auto scaling is not supported yet, this can be used as a scalable solution to build OS X Safari, iOS Simulator at scale, for automation.
    b) Many companies providing "Mac Mini Cloud" including Apple XCode Cloud (beta) for device testing.
    c) With AWS bare metal instances, you can scale Android Emulators to any limit.
    d) With legacy IE discontinuing in June 2022, one less browser to worry about.
    e) Proprietary solutions like MacStadium Okra which allows to run OS X as a container in K8s is bound to change the game.
     

    Solution:

    Going by Mobile Test Pyramid, bottom most layer uses desktop browser to emulate mobile devices' break points, to test the responsiveness of the pages, example would be Chrome Emulator. Scalable solution to this can be implemented using cloud providers like AWS / K8s combined. Second layer of the Mobile Test Pyramid uses Android Emulator/iOS Simulator, again with AWS/GCP/Azure and other OS X cloud providers, iOS Simulator/OS X Safari/Android Emulator can be implemented at scale. Most of the use cases of mobile web can be tested on emulators/simulators and can be implemented at scale using cloud providers, mobile apps may have some exceptions. For mobile web testing, there is no need to test bluetooth, gps, battery drain, calling, etc The top layer of the pyramid, real devices can be used from cross browser platforms to do sanity cases, thus keeping the cost down.
15:45

    Break - 45 mins

16:30
17:00
  • schedule  05:00 - 05:45 PM IST place Zoom people 208 Interested star_halfRate

    Software development can be a real grind, but one thing that makes it more bearable is the joy of a passing build. Not only is that green bar important when you're iterating on a feature, but it's normally a vital part of determining whether or not your software can be released. Getting to a green build as quickly as possible allows you to experience the joy of a passing build more frequently, and allows you to verify that the next release is good more quickly than your competitors. It's a vital building block as we move towards Continuous Deployment. Given how important fast builds are in your software development, how can you make the most of Selenium 4 to help get you there? In this Keynote, Simon Stewart, Selenium Project Lead & Creator of WebDriver, covers how automation frameworks can make your life easier and your builds faster and shows how you can best use them to help reduce your build times.

18:00
  • Added to My Schedule
    keyboard_arrow_down
    Dan Cuellar

    Dan Cuellar - Lightning Talks

    schedule  06:00 - 06:45 PM IST place Zoom people 206 Interested star_halfRate

    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.

19:00
  • schedule  07:00 - 07:45 PM IST place Zoom people 140 Interested star_halfRate

    Have you ever wondered what it takes to build a device farm from scratch? Wonder no more. All the details can be yours. Beyond the basics of building a complex system from the ground up, the exciting and painful experience of treading into the unknown of undocumented Apple libraries will be covered.

    The story includes the technical side of how to tread into the unknown, as well as the sociopolitical side of bringing an open source project into being. Open source can be intimidating, and this is a success story of the value in openly embracing the community, even when it seems impossible due to business requirements.

    Technical topics that will be discussed:

    • Acquiring video from Apple devices
      The different methods to do so will be explained, along with their pros and cons.
    • Remotely controlling Apple devices
      Behind the scenes of how this is done with Appium, which in turn uses WebDriverAgent, which in turn calls XCUITest functions.
    • The internal guts of Apple/Host communication ( "lockdown" protocol )
      All about libimobiledevice, reverse engineering, and proprietary Apple formats.
    • Working with a legacy NodeJS project, and the challenge of maintenance

    Regardless of your experience level or technical knowledge, you'll get a glimpse into what it takes to bring a device farm into existence from nothing.

     

     

     

     

  • schedule  07:00 - 07:45 PM IST place Zoom people 113 Interested star_halfRate

    Mobile application automation is a formidable approach to decreasing testing time and cost while increasing confidence in testing coverage. However, mobile application automation is complicated given the lack of open source tools, device fragmentation, complicated native application development, and loss of time-to-develop compared to web-based automation. However, we are fortunate to bridge the years of mobile application automation from its current infancy to further maturity via AI & machine learning assistance; thus, creating codeless (scriptless automation). AI assistance can put forth even further value to mobile application automation by also offering a solution to assist script-based automation in finding and generating correct technical identifiers. This helps alleviate the major pain point of flaky & unreliable test scripts, so that testers may focus more time on the important things, like the never-ending checklist of testing, and less time on maintaining & tweaking unreliable scripts, all while keeping the traditional, programmatic approach to automation.

  • Added to My Schedule
    keyboard_arrow_down
    Justin Ison

    Justin Ison / Anand Bagmar - It's the 20's! So why are we still testing like it's yesterday?

    schedule  07:00 - 07:45 PM IST place Zoom people 103 Interested star_halfRate

    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.

Appium Conf Day 2

Sat, Sep 18
10:00
10:30
  • Added to My Schedule
    keyboard_arrow_down
    Corina-Adina Pip

    Corina-Adina Pip - How Testers Add Value to the Organization. But also, to ourselves

    schedule  10:30 AM - 12:00 PM IST place Zoom people 203 Interested star_halfRate

    What really is the role of a tester? What activities can we perform on a daily basis, to help the company we work for achieve its goals? Should we focus only on finding and logging bugs? Or can we contribute with much, much more? Do we, as testers, see the whole picture, and are we as involved in the software development process as we could be? Do we shine and put in our best effort at work? 

    In this talk I will highlight how many activities we, as testers, can contribute and provide valuable input to. Our product experience, talent and our analytical thinking can help shape requirements, speed up delivery, improve customer experience or improve faulty processes. We can make a difference in how we achieve quality in an organization by getting more involved. And in turn, all of this will help in our personal development and in us being recognized as highly skilled, amazing professionals.

12:00
12:45

    Lunch Break - 75 mins

14:00
  • Added to My Schedule
    keyboard_arrow_down
    Rajdeep Varma

    Rajdeep Varma - Tracing the path of Appium command

    schedule  02:00 - 02:45 PM IST place Zoom people 130 Interested star_halfRate
    If you have a car and you drive occasionally, all you had to learn was driving. You don't really need to worry about how the engine or transmission system works. But what if you are a professional driver who is on the road most of the time? knowledge of what's under the bonnet can save your day if your vehicle breaks down.
    A beginner Appium user doesn't need to worry about the internal details of Appium, But, to become an Appium ninja, you need to know how it functions and if possible fix it yourself.
     
    In this demonstration, I will walk you through the journey of an Appium command from your automation code upto the action that takes place in the device. In this journey, there are series of events that take place. To make it more interesting, I will connect these events with some past GitHub issues (or current issues if anything is open when the conference takes place in September) and highlight the exact point where they take place. 
     
    I will give this walkthrough by putting debugger in IDE(AndroidStudio and VS Code) for appium-espresso-driver. 
     
    Outcome: After watching this demo, attendees will understand 
    1. How Appium for android works under the hood
    2. Find out how to work around some issues
    3. Raise more informative issues on Appium's GitHub repo
    4. Raise Pull Requests with fixes 

     

  • Added to My Schedule
    keyboard_arrow_down
    Shoban Babu

    Shoban Babu - Getting started with XCUITests

    schedule  02:00 - 02:45 PM IST place Zoom people 105 Interested star_halfRate

    Overview:

    Automation Testing on iOS applications has been highly standardized by Apple. Apps undergo rigorous checks before they receive approval to appear on the App Store. 

    It is imperative that iOS developers/testers build and maintain automation test cases to test apps that align with Apple’s regulations. They ensure that successive deployments of an app are working fine. For this, testers can use the XCUITest to ensure the quality more.

    This session will discuss the role of automation, XCUITest itself, and how to get started with it.

  • Added to My Schedule
    keyboard_arrow_down
    Rajni Singh

    Rajni Singh - Deciphering the way data is tested : Automate the movement, transformation & visualization of data

    schedule  02:00 - 02:45 PM IST place Zoom people 78 Interested star_halfRate
     

    What is the quality of data?

    Is it good enough to be collected, consumed, and interpreted for business usage?

    And how should we use this data?

    Many more question when a tester involve in testing application with big data, AI, IoT and analytical solution.

    Ambiguity has always been a key challenge for testers - be it with the ambiguous definition of requirements or with unstable test environments. But testing a data, big data workflow adds a completely new level of uncertainty to a tester’s life for modern technologies. 

    Data Validation is simply verifying the correctness of data. The Big Data Testing Pipeline consists of horizontal workflows where data transformations occur continuously, managing a series of steps that process and transform the data. The obtained result can be settled into a database for analysis(Machine Learning Models, BI reports) or act as an input to other workflows.

    This session is to provide a solution to challenges faced while data testing for an application (with big data, IoT, a mesh of devices, artificially intelligent algorithms) and with data analytics, like:

    1. Lack of technical expertise and coordination
    2. Heterogeneous data format
    3. Inadequacy of data anomaly identification
    4. Huge data sets and a real-time stream of data
    5. Understanding the data sentiment
    6. Continuous testing and monitoring

     

    The research employed an open-source solution for the implementation. Apache Kafka was used to gathering Batch data and Streaming data (Sensor/Logs). Apache Spark Streaming consumed the data from Kafka in Realtime and carried out the validations in Spark Engine. Further in the workflow, the data was stored in Apache Cassandra and then configured in Elasticsearch and Logstash to generate real-time reports/graphs in Kibana. The proposed tool is generic as well as highly configurable to incorporate any open-source tool you require to work within streaming, processing, or storing the data. The system includes configuration files where every single detail of the dependent tool used is appended and can be modified according to the needs.

     

    This solution aims to analyze various Key performance indicators for Big Data like data health check, downtime, time-to-market as well as throughput, and response time. The tool can be considered as a pluggable solution that can efficiently drive big data testing and uplift the data quality for further usage.

    Attend this session to understand the basic need of future application testing.

    1. Understanding of data and importance of data quality
    2. Why automation is an essential strategy for data testing.
    3. Vertical continuous flow for data and the horizontal flow of data in the pipeline.
    4. Potential solution demo with an implemented use case for real-time experience
    5. Generic code will be shared with attendees for enhancement.
    6. KPI's consideration for data validation.
     
15:00
  • Added to My Schedule
    keyboard_arrow_down
    Dimpy Adhikary

    Dimpy Adhikary / Rashmi Konda - UIAutomator2 & Espresso drivers - The Perfect Duo for MQTT (IoT)

    schedule  03:00 - 03:45 PM IST place Zoom people 103 Interested star_halfRate

                     Appium has came long way with the evaluation of different drivers. The journey of providing support for blackbox testing to graybox is just phenomenal. We face many real time issues while testing our apps right from flaky tests to areas which cannot be tested with blackbox testing approach. In android platform, UI automator driver has matured level but we cannot still test areas which needs access to the application code. Luckily we have a bridge now which can help us to use both black box and graybox testing in the same time, yes we are taking about Espresso driver. In this session we will be covering some of the interesting aspects of both the drivers (UIAutomartor2 and Espresso) and explore in detail the pros and cons of both via a demonstration.

    Problem Statement: While testing a native IOT application, we could figure it out the following issues using blackbox automation approach.

    • The validation of the style attributes (for example the change in colour of an element based on event)
    • Testing notifications
    • Synchronization of the script due frequent UI element update via async API calls
    • Testing two applications together one release app and another debug app
    • Need of accessing of native components of  Android

    Solution: After doing a close review and analysis we could realise that using just one appium driver will not be enough to overcome all the issues listed above. Carefully selecting the best of UIAutomator2 and Espresso driver we could get the desired output and found the perfect duo for our use case. In this presentation we will be demonstrating the same how we have done the end to end testing of an IOT application (M2M communication) using appium UIAutomator2 and Espresso drivers.

  • Added to My Schedule
    keyboard_arrow_down
    Andy Chumak

    Andy Chumak - Test automation on the living room devices

    schedule  03:00 - 03:45 PM IST place Zoom people 75 Interested star_halfRate

    Have you noticed how many new streaming services have popped up over the last few years? Not only Netflix and HBO, but also Disney+, Apple TV and many more global and regional brands. The streaming / entertainment industry is booming, which means someone has to develop, test and deliver all those streaming applications for every device that is capable of video playback – from your mobile phone and desktop browser to Smart TVs, streaming sticks and set-top boxes. But how do you automate tests on all these exotic platforms?

    In this talk you will learn which tools are currently there, what their strong and weak sides are, and how Appium 2.0 and its upcoming driver's ecosystem can change the rules for test automation on living room devices.

  • schedule  03:00 - 03:45 PM IST place Zoom people 118 Interested star_halfRate

    A common root cause of failures in end-2-end (e2e) automated tests is unpredictable backend API behaviour. This results in the test executions being flaky. But if you think about this, you also should be testing the impact of such unpredictable backend API behaviour on the app under test.

    The question then remains — how do you implement a deterministic e2e test that validates how the app handles such unpredictable situations.

    In this talk, we will take you on the journey in which a team at Jio created a testing ecosystem for running e2e tests against our mobile app using Appium and at relevant points in the flow, we set dynamic contextual expectations on the Specmatic stub to simulate the desired behaviours.

15:45

    Break - 45 mins

16:30
17:30
18:00
18:25
help