Mobile application test automation with Appium. Without coding.

  • Step 1 — Setup of Testing Environments
  • Step 2 — Create the Test Case
  • Step 3 — Run & Report the Test Case

Step 1 — Setup of Application, Robot & Environments

  1. Upload the mobile application on the device
  2. Configure the robot to interact with the device
  3. Define the testing environments of the application.

1.1. Upload Your Mobile Application

1.2. Create The Testing Robot

  • Type: Choose either IPA for iOS devices, or APK for an Android one.
  • Platform: Choose the correct one depending on your first option.

1.3. Create The Application

  • Type: Select the same mobile application typology as previously.
  • System: Select to which system this application belongs to.

Step 2 — Create The Test Case

2.1. Create the Test Case Header

  • Test Folder: Select in which folder you want to keep your test cases. Here choose “Demo”. The folders can be managed in the “Test / Test Folder” page.
  • Testcase ID: Enter your custom ID or leave the default generated one.
  • Test case short description : Enter one-line description, usually in a use-case format “As a <user>, I want to do <use-case> and verify <controls>”
  • Application: Select the application under test, in our case “SampleBSAPK”

2.2. Define The Step, Action and Control

  • Action openApplication: Open the application set in the Application definition.
  • Control takescreenshot: Will take a full screen screenshot (defined it for the sake of demonstration as they can be taken automatically if needed).
  • Action click: Click on the recognized element.
  • Element path xpath=//input[@name=’btnK’]
  • Control verifyElementTextEqual: In this case, we will verify if the result of our operation is as expected in the result area. A lot of other controls are available and described in the documentation.
  • Action closeApplication: Close the application to end the session with the robot acting as the interface between your test and the device.
  • This will avoid the test to remain pending and liberate the session.

Step 3 — Run & Report The Test Case

3.1. Launch the Test via the Run Test Page

  • Environment: Select one or more environments where the Test Case should be executed. In our case, pick “QA” or “PROD”.
  • Country: Check one or more countries where you would like to run the Test Case. Pick “UK”.
  • Robot Settings: Define the mobile app hub where the Test Case will be executed upon. In addition, you can integrate with other remote testing farms such as LambdaTest, Kobiton, Saucelabs among others.
  • Execution Settings: Mainly related to the traceability levels for the test, test infrastructure and queuing mechanisms (retry, priority, …).

3.2. Follow the Test Case Execution

3.3. Analyze The Test Case Report

Troubleshooting guidelines

  • Verify your Application definition, especially for the test environment and country. If you encounter a message related to those parameters this is probably the problem.
  • Verify your Test Case activated Environment. If you cannot launch your test in a Production environment you will need to explicitly activate it in the Test Case Header.
  • Verify your Robot is correctly running and accessible on the ports you configured. You can manage them on the “Run/Robots” page.

Accelerating Your Mobile Testing Automation

  • Clap this article 👏
  • Star the project on GitHub
  • Offer a coffee



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Cerberus Testing

Cerberus Testing

Cerberus Testing is then 100% open-source test automation platform to accelerate software delivery. Stop coding, start testing.