A Fast Route to Appium with Oxygen

Mobile testing brings additional challenges to both developers and QA engineers. Manual testing of an application on dozens of devices, all with different hardware and software specifications, is a nightmare. Being able to easily and quickly testing an application on wide range of devices and operating systems in mandatory today for almost every mobile project.

Since Selenium and Appium open source frameworks have been release, test automation sees a renaissance. What started as a developer oriented tool has now became a de-facto standard for web and mobile automation testing. Yet many testers strangle to start working with Appium as it requires extensive programming skills and mobile app development background.

In this session you will learn how to easily and quickly create automated tests for mobile applications based on Appium. We will talk about Oxygen – Selenium and Appium based open source framework that greatly simplifies working with Appium, solving many complexities of it.

We will outline the best practices for simplifying mobile testing and Appium onboarding process, sharing the best practices and common issues that Appium users are facing every day.


Outline/Structure of the Tutorial

  • Appium setup and main concept
  • Test automation principals
  • Oxygen overview
  • Recording and inspecting UI elements
  • Creating and running a first test on Android
  • Data-driven testing
  • Test suites and reporting
  • Test automation in iOS
  • Running tests on cloud devices

Learning Outcome

  • Appium overview
  • Getting started with mobile test automation
  • Android and UIAutomator testing
  • Oxygen - test automation framework for web and mobile
  • Testing on devices in cloud

Target Audience

Manual Tester, QA Engineers, Web Automation Engineers

Prerequisites for Attendees

  • Basic understand of QA concepts and mobile technologies
  • Previous test automation experience is an advantage
schedule Submitted 1 year ago

Public Feedback

comment Suggest improvements to the Speaker
  • Anand Bagmar
    By Anand Bagmar  ~  1 year ago
    reply Reply

    Hi Nahum,

    Since you have submitted this as a tutorial, what will be the working mechanics of this? Will attendees be doing some coding along with you? 

    If attendees are not going to be doing any hands-on activities with this, do you think 90 mins of just listening and watching may be too long from an information perspective? Have you done this type of tutorial before?

    Another thought - what if you change / tune the content to make it fit in 45 min - with very specific topics core to your content?

    • Nahum Dimer
      By Nahum Dimer  ~  1 year ago
      reply Reply

      Hi Anand,

      90 min for fully hands-on session is too short I believe, as I will need them to make sure all the attendees are on the same track as demo progresses (unless there will be only few attendees). From my previous experience (I do a similar presentation every 2-3 months in Israel on various meetups), some attendees do use their laptops to keep up with the demo, but most are taking notes. This is very dynamic and practical session so I don't think the audience will be bored even without in-sync hands-on. We will make sure they get the presentation home, so they can get some hands-on at home and be able to ask questions later on to close the gap between "dry" demo and the hands-on.

      That said, I don't mind to shorten it to 45 minutes. This is enough time to show them a basic walkthrough how to start with Appium and Oxygen. However, I won't be able to show how to run the tests in cloud and talk in depth about how to make mobile automation testing more efficient (reducing maintenance, eliminate flaky results, etc.).