Home

Awesome

Getting started with the Robotframework-AppiumLibrary - RoboCon 2021 and 2022 Workshops

General Information

This repo contains all of the examples that will be covered in the "Getting started with the Robotframework-AppiumLibrary" online workshop (click here to watch a walkthrough on YouTube). The core audience for this workshop are beginners but there's also content mentioned below that could be interesting to more advanced testers as well. A lot of the examples kept in this repo were heavily influenced by the Robot-Framework-Lone-Tester-Strategies-RoboCon-2019 and Tool-Strategies-Lone-Testers-Test-Leadership-Congress-2019 work and experiments I have done in the past. More information about this RoboCon 2021 workshop can be found here... https://robocon.io/#workshops

Bonus Content: There are some possibly interesting extras in the repo that I did not mention in the original workshop bio. They are...

Updated Content: Everything in this repo will be used in the Getting started with the Robotframework-AppiumLibrary - RoboCon 2022 In-person Workshop, and will be combined with the following...

The following are the basic technical requirements to run the examples during the workshop.

After installing the basic technical requirements on your machine (depending on the OS: Windows, MacOS, Linux etc.) please run the following on your machine.

git clone https://github.com/jg8481/Getting-Started-Robotframework-AppiumLibrary-RoboCon-2021-And-2022.git
cd ./Getting-Started-Robotframework-AppiumLibrary-RoboCon-2021

Set up an .env file using the provided template.env file.

Workshop Examples

There will be presentation slides explaining the following in more detail and I will assist everyone with running them. The examples will automate the following apps.

If the BrowserStack WikipediaSample.apk link stops working you can try these links.

  1. Workshop-Part-One: Simple automation workflows for IOS apps and automation workflows for Android apps + adb shell.
>> Following commands need to run first before any other examples in Workshop-Part-One. <<
bash ./start-specific-appium-example-workflows-for-workshop.sh All-Appium-Tests-Teardown &&
bash ./start-specific-appium-example-workflows-for-workshop.sh Appium-No-Proxy-Test-Setup

>> Each command runs a group of examples for Workshop-Part-One. <<
bash ./start-specific-appium-example-workflows-for-workshop.sh Robot-Framework-Android-Apps-And-Adb-Tests Android_Adb
bash ./start-specific-appium-example-workflows-for-workshop.sh Robot-Framework-Android-Apps-And-Adb-Tests Android_App_Recording_Screen_Capture
bash ./start-specific-appium-example-workflows-for-workshop.sh Robot-Framework-IOS-App-Tests
bash ./start-specific-appium-example-workflows-for-workshop.sh Robot-Framework-IOS-And-Android-Mobile-Browsers-Test-Examples

  1. Workshop-Part-Two: PaBot, Charles Proxy, Graphwalker, and adb shell CPU usage monitoring workflows.
>> Following commands need to run first before any other examples in Workshop-Part-Two. <<
## The following two setup commands are only for the Charles Proxy examples.
bash ./start-specific-appium-example-workflows-for-workshop.sh All-Appium-Tests-Teardown &&
bash ./start-specific-appium-example-workflows-for-workshop.sh Appium-Charles-Proxy-Test-Setup
## The following two setup commands are only for the PaBot Parallel IOS and Android device examples.
bash ./start-specific-appium-example-workflows-for-workshop.sh All-Appium-Tests-Teardown &&
bash ./start-specific-appium-example-workflows-for-workshop.sh Appium-No-Proxy-Test-Setup

>> Each command runs a group of examples for Workshop-Part-Two. <<
bash ./start-specific-appium-example-workflows-for-workshop.sh Robot-Framework-Charles-Proxy-IOS-And-Android-Mobile-Browsers-Test-Example
bash ./start-specific-appium-example-workflows-for-workshop.sh Robot-Framework-Parallel-IOS-Android-Tests

The Workshop Examples use a lot of Bash scripting for setting up Appium and running Robot Framework. If you have a Windows operating system, the following options may work for you...

Big thank you to the following people and groups.

Their contributions to the testing community helped me a lot with this workshop and my day-to-day work.