With the advancements in the IT industry, the mobile app development is getting more and more widespread. But to be sure that the apps do not end up being released in a broken state, testing is required. While manual testing approach can certainly do the job, more and more projects are interested in automating their testing process. One of the most popular tools for mobile automation is Appium. But setting Appium up can be a confusing process. Today, we will take a look at how things should be done in order for your automation tests to start. This guide will encompass both iOS and Android-specific things, so you will not have to worry about only one platform working. But before we get to that, let’s discuss the advantages of Appium, as this is our Automation tool of choice. Why Appium? First of all, it is free and open-source, and has a huge base of users, so if you run into any issues, you can be sure that you can find help online. Another advantage of Appium is that it can give you the capability to work with native, hybrid and web-apps, not to mention that Appium supports a variety of programming languages, such as JavaScript, Python, Ruby, C# and Java, so most of the programmers can start automating without a need to switch their language of choice. Also, it supports cross-platform testing, meaning that if you want to make sure that your mobile application flows are the same regardless of the platform, this tool is right for you (it should be mentioned, however, that device-specific things like permissions are still handled a little differently). However, while having those significant advantages, it also has some disadvantages, such as a complex setup. But with this guide, you can find out how to do it without the need to search for extra information in all corners of the internet. Let’s begin. How do I choose an Appium version? First things first, it should be mentioned that there are a lot of differences between 1.x and 2.x versions of Appium. of Appium support some useful features as automatic permission granting for iOS devices specifically. Also, it does have a server GUI, so interactions with the server are much more clear and intuitive. 1.x versions While of Appium do not have some of the good stuff that do, it is the latest (as of the moment of writing this article) release of Appium, which means active support. Another advantage of of Appium is the plugins and drivers availability. 2.x versions 1.x versions 2.x versions In this guide, we will be taking a look at how to install and set up the Appium specifically. 2.x Installing Appium As a prerequisite, you should install Node.js and npm package manager. This can easily be done on the official . Simply download and install the latest stable version and you’re good to go! If you don’t know whether you have a node and npm installed already, you should run the following commands in your terminal to check: node.js website To verify node installation, use this command node -v To verify npm installation, use this command npm -v After that, you are ready to install the Appium itself, which is also done in one simple command in your terminal: npm install -g Appium After that, the Appium should be installed globally on your machine so you don’t have to worry about running this command in your workspace folder. But this is not the end of the process; the next step would be to prepare the Java development kit, as well as the tools you will need for working with Android and iOS apps. Installing JDK You can find the latest JDK freely available on the . Download and install it. After that, you should set up the JAVA_HOME environmental variable. oracle website Let’s take a look at how to install it on : Windows Go to and type . As a result, you should see a control panel element. Open it. “Start” “View advanced system settings” After that, make sure you’re on the tab of the opened window and press the button. “Advanced” “Environment variables” In the section, click the button. “System variables” “New…” Set as a variable name and the path to the JDK as a Variable value. By default, it should be ***C:\Program Files\Java\jdk2.1 ***(keep in mind which version you install, the numbers at the end could be different) “JAVA_HOME” For , you can do this by executing the following command in your terminal: Mac users If you use bash, use: echo export “JAVA_HOME=\$(/usr/libexec/java_home)” >> ~/.bash_profile If you use zsh, use: echo export “JAVA_HOME=\$(/usr/libexec/java_home)” >> ~/.zshrc By following these steps, you have successfully set up the JAVA_HOME environment variable, but there is still more work to do, so let’s get to it. The next step would be installing the Android Studio. To do this, simply go to the , download and install it for your respective OS. Android Studio website Installing Android SDK and SDK tools Once you have Android Studio ready to go, you should install Android SDK by following these steps: Open the Android Studio Click “More Actions” -> SDK manager Go to “Appearance and behavior” -> System settings -> Android SDK Click on the checkbox near the respective Android version you need to install (Example: Android 10.0 (Q)). Click the download icon that appears to the left of the Android X.X label Click at the bottom of the Android Studio window “Apply” Also, check if the Android SDK location is set up properly. It should be displayed near the top of the Android Studio window and should look like this: C:\Users\user\AppData\Local\Android\Sdk Lastly, go to the SDK Tools in your Android Studio and check if you have the following components installed: Android SDK build tools Android SDK platform tools Android SDK command-line tools If you do not have some of those components installed, install them similarly to steps 4-6 of the Android SDK installation. The next step would be to add an environment variable. ANDROID_HOME Adding android_home environment variable For , the process is similar to JAVA_HOME: Windows Go to and type . As a result, you should see a control panel element. Open it. “Start” “View advanced system settings” After that, make sure you’re on the tab of the opened window and press the button. “Advanced” “Environment variables” In the section, click the button. “System variables” “New…” Set as a variable name and the path to the Android SDK as a Variable value. By default, it should match the Android SDK location that is set up in your Android studio: “ANDROID_HOME” C:\Users\<username>\AppData\Local\Android\Sdk However, that is not all. We should also update the Path variable. In order to do that, find the PATH variable in the list, click on it, and then click In the opened window, click and add enter the path for SDK platform tools: “System variables” “Edit.” “New” C:\Users\<username>\AppData\Local\Android\Sdk\platform-tools Then, repeat this process and add SDK tools to the path variable: C:\Users\<username>\AppData\Local\Android\Sdk\tools Also, add the path to SDK/bin folder: C:\Users\<username>\AppData\Local\Android\Sdk\tools\bin Save the changes by clicking “OK”. For , the first steps are similar: download and install Android Studio and the respective sdk componends. mac/linux users The variable, however, is set up from the terminal. After you’ve done the necessary steps in the Android studio window, open the terminal. ANDROID_HOME If you use bash, do the following: Open .bash_profile: nano ~/.bash_profile Add the following lines to the file: export ANDROID_HOME=$HOME/Library/Android/sdk export PATH=$PATH:$ANDROID_HOME/platform-tools export PATH=$PATH:$ANDROID_HOME/tools export PATH=$PATH:$ANDROID_HOME/tools/bin export PATH=$PATH:$ANDROID_HOME/emulator Save the changes in the file and reopen your terminal If you use zsh, the process is similar: Open .zshrc: nano ~/.zshrc Add the following lines to the file: export ANDROID_HOME=$HOME/Library/Android/sdk export PATH=$PATH:$ANDROID_HOME/platform-tools export PATH=$PATH:$ANDROID_HOME/tools export PATH=$PATH:$ANDROID_HOME/tools/bin export PATH=$PATH:$ANDROID_HOME/emulator Save the changes in the file and reopen your terminal This covers the environment variables for Android. Now, let’s take a look at how to prepare for iOS testing. Preparations for iOS testing Unfortunately, in order to launch an iPhone or iPad simulator, you need to have a Macbook available. But once you open it, what’s next? This guide will help you prepare to automate the iOS app tests. The first thing you should do is install XCode. To do that, open the App Store on your Macbook, log in to the Apple account, and get the xCode. It is available for free. After that, make sure you have command-line tools set up properly by going to and checking the . If you have nothing there, simply click on the list and choose . Xcode -> Settings -> Locations “Command line tools” section “Xcode X.X.X” Then, check if you have all the available platforms for your app tests. To do that, go to . To add a platform version, click the button at the bottom left of the window, select and download the package for the needed iOS version Simulator. Xcode -> Settings -> Platforms “+” “iOS,” With that, you should have your Simulators ready for iOS testing. The next step would be installing the drivers for iOS and Android automation. Installing xcuitest and uiautomator2 drivers Installing those drivers is also simple. To do that, open your terminal and run the following commands: For xcuitest: appium driver install xcuitest For uiatomator2: appium driver install uiatomator2 It should also be noted, that sometimes, the installation could crash depending on your npm version. If you have any issues while running those commands, the first thing you should try is downgrading your npm version to around 6.0. Now that you have the environment and drivers set up, we can get around to installing the Appium Inspector. Installing Appium Inspector It can be found on the . Download and install it for your respective OS. To be able to write your tests, you’re going to need to obtain selectors for the elements of your app. For that, we have to install an Appium Inspector. Appium Inspector Releases GitHub page Once you open the Appium inspector, make sure you have text in the input field. “/wd/hub/” “Remote path” Next, we will have a look at how to open your Simulator in your Inspector to get the elements. We should start by launching the Appium server. Starting the Appium server To start the Appium server. To do that, open the terminal, and run the following command: appium –base-path /wd/hub/ If you have done everything correctly, you’re going to see in your terminal: as well as “Appium REST http interface listener started on http://0.0.0.0:4723/wd/hub” “Available drivers: xcuitest uiatumator2” It means that the server has started successfully, and the drivers are installed and usable. Leave the Appium server running in the background, and do not close the terminal. If you have any issues with the Appium launch, now is the time to troubleshoot them. Troubleshooting Appium installation In order to check what’s wrong, you can use a helpful tool called appium-doctor. Install it using the following npm command in your terminal: npm install appium-doctor -g After that, to check the Appium status simply execute this command in your terminal: appium-doctor This should give you an idea of which components are still missing on your machine. In any case, after you’ve taken care of them, it’s time to go back to the Inspector and set the Appium capabilities. Setting the Appium capabilities In order for your Inspector to know which Simulator to check, you should set the capabilities. Go to the Desired capabilities and click the button to add a new one. The core capabilities are the following: “+” should be the same as the name of your Simulator. For example: “iPhone 14 Pro” or “Pixel 6” appium:deviceName – should be “iOS” or “Android” appium:platformName – should correspond to the iOS or Android version of the Simulator (Example: “16.0” for the iPhone on the 16.0 version of iOS or “13” for Android with OS version 13) appium:platformVersion – – should be “XCUITest” or “UiAutomator2” for iOS and Android devices respectively appium:automationName These are the core capabilities with which you will be able to connect to your Simulator via Appium Inspector. Finally, you have set up Appium and the necessary things for it and created your first automated test, but how do you run it? In order to do that, we will have to set up a wdio project. Setting up the wdio project Starting a wdio project is not complicated at all. In order to do that, just execute the following command in the terminal, make sure to do it in the directory where you want your project to be located. After you’ve changed directories in the terminal to the folder of your choice, execute the following command: npm init wdio@latest After doing that and following the instructions given in the installation process, the next thing to do would be to set up the wdio config file. Setting up the wdio config If you need to test the app on both iOS and Android, you’re going to need two different configs. Let’s name the iOS config and the Android config They will be mostly similar, but the key difference will be the capabilities defined in the config. Since you will not need an Appium Inspector to run the tests, the capabilities for your devices are defined here. “wdio.ios.conf.js” “wdio.android.conf.js.” Here is an example of how the wdio.android.conf.js file should look like: path: ‘/wd/hub/’,  

    runner: ‘local’,  

    specs: [‘./path/to/specs/*.js’],  

    maxInstances: 1,  

    capabilities: [  

        {  

            ‘appium:platformName’: ‘Android’,  

            ‘appium:platformVersion’: ‘13’,  

            ‘appium:automationName’: ‘UiAutomator2’,  

            ‘appium:app’: ‘./path/to/your/application/app.apk’,  

        },      

        ],  

    port: 4724,     

    services: [  

        [‘appium’,  

            {  

                args: {  

                    relaxedSecurity: true,  

                    basePath: ‘/wd/hub’,  

                    address: ‘localhost’,  

                },  

                command: ‘appium’  

            }  

        ]  

    ],  

    logLevel: ‘debug’,  

    bail: 0,  

    waitforTimeout: 15000,  

    waitForInterval: 200,  

    connectionRetryTimeout: 90000,  

    connectionRetryCount: 3,  

    framework: ‘mocha’,  

    mochaOpts: {  

        ui: ‘bdd’,  

        timeout: 120000  

    }, The config setting should contain the path to your specs, while the capability should contain the path to the application for which the tests are written. The capability should point to the or file for Android or iOS, respectively. You can find more configuration capabilities on the . Ok, now you have some tests written and config set up, but how do you run the tests? specs appium:app app .apk .app official webdriverIO website Running the tests After which, make sure your Appium server terminal instance is closed (or a different port is specified in the wdio.conf.js file); also, check that your Simulator device is open. Then, in the terminal, run the following command: In order to run the tests, make sure the config has the correct path to the app and the test specs set up. npx wdio run wdio. Android.conf,js This is an example of a command that will run your Android tests. Make sure the name is corresponding to your .conf.js file name. If you want to run the iOS tests using this example, then use the following command: npx wdio run wdio.ios.conf,js But if you do not need to run all the tests at once, you can also use the following command: npx wdio run wdio. Android.conf,js –spec specName.spec.js This command will only run the tests defined in the file. specName.spec.js , you now have the knowledge on how to install Appium and all the necessary things for you to start your journey of mobile testing. Also, here are some useful links to help you figure out the Appium and Wdio commands to write the tests themselves: In conclusion Appium documentation Wdio documentation

This story contains new, firsthand information uncovered by the writer.

Walkthroughs, tutorials, guides, and tips. This story will teach you how to do something new or how to do something better.

A Guide to Setting up Appium (with WebdriverIO) and Run Tests for IOS and Android

About Author

Comments

TOPICS

THIS ARTICLE WAS FEATURED IN

Related Stories

Untitled Story

For QA Engineers: How to Use Android Debug Bridge in Mobile Application Testing

Real Devices vs Emulators vs Simulators for Mobile App Testing

The Noonification: Patience is Beautiful (6/18/2023)

Appium Testing for Flutter Apps

How to Run 5000+ Tests on Mobile Devices Everyday; From inDrive's Playbook (Part 1)

For QA Engineers: How to Use Android Debug Bridge in Mobile Application Testing

Real Devices vs Emulators vs Simulators for Mobile App Testing

The Noonification: Patience is Beautiful (6/18/2023)

Appium Testing for Flutter Apps

How to Run 5000+ Tests on Mobile Devices Everyday; From inDrive's Playbook (Part 1)

Light-Mode

Classic

Newspaper

Dark-Mode

Neon Noir

Minty

HN StartUps