Skip to main content

Executing appium tests on Android mobile web

Back to Appium Tutorial Index

Having set up appium, lets run our first tests. But before that start the appium and android device /  emulator as following -

navigate to appium installation, which is following on my Ubuntu -
/home/tarun/node-v0.12.2-linux-x64/bin
and start appium from command line or using Appium Desktop app
./appium
Open another command prompt and execute -
adb devices
and you should see list of devices attached as -
List of devices attached
emulator-5554    device
If you see any error message then re-verify all the steps mentioned earlier to make sure none of the step is missed

Sample JUnit project to run tests on android emulator
  • Clone the following appium project -
git@github.com:tarun3kumar/appium-tests.git
  • Import project in IDEA (or your favorite IDE) and Open AndroidEmulatorWebTest class -
AndroidTools.png

  • Right click on method testMobileWebOnEmulator and click Run. This would execute test on android emulator -
AndroidTools.png

Sample JUnit project to run tests on android device

Use the same project but AndroidDeviceWebTest class to run test on mobile device. Of course you need to have device setup as explained in previous steps

Popular posts from this blog

Which location strategy to use with mobile apps

Locator Strategy for native mobile apps IDs and accessibility locators are still king. NSPredicate (iOS) and UIAutomator (Android) are great—mainly better than XPath —but they do not beat a good accessibility id or resource-id . And CSS selectors don’t exist for native apps (only for WebViews). Locator Strategy Ranking Rank iOS (native) Android (native) Why 1 Accessibility ID → name / label (via MobileBy.AccessibilityId or @iOSXCUITFindBy(accessibility = "Mehr anzeigen") ) Accessibility ID → content-desc (via MobileBy.AccessibilityId ) or @AndroidFindBy(accessibility = "Letzte Aktivitäten, Überschrift") ) Fast, readable, stable when set intentionally; improves a11y. 2 Stable identifiers (rare on iOS) resource-id (via new UiSelector().resourceId(...) ) or @AndroidFindBy(id = "load_more") id is just shorthand for matching the native Android resource-id attribute. Appium automatically maps id → resource-id If you pass only "load_more"...

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 -