We will discuss the working of Appium in both Android and iOS separately.
Once the Appium server is up, it follows the Grid concept to send tests to the device. Once Appium server shares the proxy commands then communication gets established through HTTP JSONWire protocol.īefore running our test case, we first start the Appium server which is the similar process as Selenium RC wherein we wait for the Selenium server to get started. Further, the device waits for the proxy commands from the Appium server. In general, we write a test case in any of our preferred programming languages to test the application on the device which internally starts the server itself. Thus, Appium creates and handles one or more than one WebDriver sessions for mobile platforms.Įach OS/platforms like Android or iOS has its mechanism to communicate with Appium server. It follows the HTTP JSON Wire protocol to send and receive commands.
But, there is a thin line of difference between Appium and Selenium grid which will be visible in the later part of the tutorials. When I started working on mobile automation through Appium a few days back then I found its working principle is the same as the Selenium Grid. Well, you will feel connected with Appium or Appium Server if you are aware of two of the most important components of Selenium i.e., Selenium Grid & Selenium RC. The agenda of this article is about the understanding of Appium Server and its architecture which demystifies the testing of mobile app and site.
This is just the beginning of the mobility section of our blog. It’s high time to switch to mobility and mobile automation testing because mobile-first is the talk of the town. We have discussed most of the web GUI automation with Selenium WebDriver.