TL;DR Summary

• Espresso is a powerful UI automation framework for the Android platform that offers gray box automation capabilities and has a simple, concise, and rich API. 
• Onboarding to use espresso can however sometimes take time. In this talk, I will explain how to get started with Espresso in the shortest time possible and we’ll look at some recipes on how to automate common app scenarios with espresso API.

Abstract

• It’s 2022 and most businesses these days are mobile-first with a presence on major platforms. UI automation is a critical part of the testing strategy of businesses looking to release high-quality apps with confidence. While unit testing is a much wider adopted practice, writing scalable UI automation is often a challenge due to its higher fidelity.

• Espresso is the dominant UI automation library for android from Google that provides a rich and concise API to test your android app's UI with confidence without sacrificing reliability and with minimal flakiness due to amazing integration with underlying instrumentation.
• For an n00b engineer approaching their first Espresso test, it could be especially tough to wrap your head around its idioms and android context and get set up quickly. 
• Well, In this talk:
  • we’ll solve for that exact persona and provide a quick understanding of an espresso test structure
  • Follow up by diving deeper into its API
  • Discuss different ready to use recipes that developers could use to solve some common use cases with mobile UI automation
  • Provide a boilerplate framework
  • I'll share Github repo links that have app source code along with their Espresso UI tests to follow along or revisit later.

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.

With an ever increasing no of businesses being conducted on web the testing need to write automated tests for the app's UI is something that can never be ignored. As you all know Selenium provides an API that enables us to do this quite effectively.

However, when tasked with setting up the automation framework, there are a lot of questions that arise in the minds of aspiring test developers regardless of what level they are in their career.

Some of such questions are:

1. How does one actually go about the business of building a robust and effective automation framework on top of selenium?
2. What are the elementary building blocks to include in the framework that an aspiring automation developer should know of?
3. How should we model our tests? XUnit style vs BDD?
4. Are there good practices, sensible design patterns and abstractions that we can follow in our code?
5. What are some of the anti patterns/common mistakes we should avoid

A lot of literature, documentation and blogs exists on these topics on the web already.

However In this talk,

I would combine this existing knowledge and my years of experience in building automation frameworks and breakdown these elements and walk you through exactly the sort of decisions/considerations and practices that you can take while starting to implement or improve the UI automation for your team.

Hope to see you there!

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.