Appium Architecture

Back to Appium Tutorial Index

Appium is an HTTP server which is written in Node.js and exposes REST API. It creates and handles multiple WebDriver sessions. It receives connections from a client, listens for commands, executes those commands on a mobile device, and responds with an HTTP response. It is same as the Selenium server, where in selenium server gets HTTP requests from Selenium client libraries.

Like selenium tests, appium tests are also written once and can be run on multiple devices (well almost). This primarily entails four entities -

Tests, written in one of the appium supported languages
Appium server (also known as test server), which interacts with device (or emulator) running the test
Device (or emulator) to run tests on
Machine from where tests are run

This could be visualized from following Appium Architecture Image

Herein one machine can be used to run both appium server and test. In Appium video tutorial we would be running appium server on the same machine on which tests are executed. Test code performs HTTP calls to server which then translates those commands into device specific actions sent to device. These commands are user interactions to the device for ex - clicking on button, swiping the screen, scrolling in to area etc

Verify email confirmation using Selenium

Note: If you are new to java and selenium then start with selenium java training videos . Email confirmation seems to be integral part of any registration process. I came across an application which lets you provide your email address. You can follow the sign up link in you mail and then complete the registration process. Lets consider we provide GMail address for it. Now if were to use only Selenium then we would have to follow following steps - Launch GMail using Selenium; Some how search for new mail in the list of available mails; Some how click on it; Parse the mail message; Get the registration link; Follow up with registration process What do you think of an approach in which you can

Selenium Tutorial: Ant Build for Selenium Java project

Ant is a build tool which could be used to have your tests running either from command line or from Hudson CI tool. There is detailed documentation available for ant here but probably you need to know only a little part of it for you selenium tests. The essentials which are needed to know are: Project Target (ant execution point and collection of tasks) Tasks (could be as simple as compilation) And there would usually be following targets for Selenium tools - setClassPath - so that ant knows where you jar files are loadTestNG - so that you could use testng task in ant and use it to execute testng tests from ant init - created the build file clean - delete the build file compile - compiles the selenium tests run - executes the selenium tests Here is my project set up for ant -

Capture network traffic using WebDriver

We often come across testing requirements when we need to analyze the network traffic to find - HTTP status of page Analyze header information to find if right information is passed Validating parameters related to ajax requests etc Selenium 1 has had a way to capture n/w traffic but the feature does not always work as expected. At times Selenium 1 does not capture all n/w traffic, And given that Selenium 1 APIs are almost dead it is

No Automated Testing

Search This Blog