I work as a software test engineer already more than 6 years. And during these 5 years, I understood one thing – if You want to start to learn something new from the beginning, then You will Google for it. And as a result – You will find a lot of information without examples and simple explanation or You will find nothing at all, except some raw documentation.
I found that topics about mobile automation sometimes scare the people. So, I want to reveal the myths about mobile automation.
This article describes the simplest way of how to setup and run Your first test. An example is based on Appium 1.5.3 and Android system. It’s not about advanced usage of the latest version, etc.
What You need for starting with mobile automation
There are few thing that You need to have.
Computer. MacBook is preferable to perform automation testing for iOS also.
Pre-installed Android SDK or Android Studio is even better. Download here.
Configured environment like for Selenium WEB testing.
Appium desktop application latest version (1.5.3). Download here.
Base configuration
After downloading of Android Studio and setup of Android SDK You need to add the path to the folder with android SDK to the PATH of environments.
Run 1st test
Create simple maven project in Eclipse or IntelliJ
Download test application that is used as an example. You can find it here or on Play Store here
Create test class based on JUnit test framework and past the code inside:
public class PresentationTest {
private static final String MYREACTIONS_ID = "com.denyszaiats.myreactions:id/";
protected static DesiredCapabilities capabilities;
@Test
public void testPresentationTapGame() throws InterruptedException, MalformedURLException {
capabilities = new DesiredCapabilities();
capabilities.setCapability("platformName", "Android");
capabilities.setCapability("platformVersion", "6.0");
capabilities.setCapability("deviceName", "emulator-5554");
capabilities.setCapability("app", {PATH_TO_APK_FILE});
AppiumDriver driver = new AndroidDriver(
new URL("http://0.0.0.0:4723/wd/hub"),
capabilities
);
driver.manage().timeouts().implicitlyWait(10, TimeUnit.SECONDS);
driver.findElementById(MYREACTIONS_ID + "imageLangEn").click();
driver.findElementById(MYREACTIONS_ID + "skip_login_button").click();
driver.findElementById(MYREACTIONS_ID + "buttonGuideOk").click();
driver.findElementById("android:id/home").click();
driver.findElementById("android:id/home").click();
driver.findElementByXPath("//*[@text='Crazy Fingers']").click();
driver.findElementById(MYREACTIONS_ID + "buttonGuideOk").click();
driver.findElementById(MYREACTIONS_ID + "handButton").click();
driver.findElementById(MYREACTIONS_ID + "imageRightHand").click();
driver.findElementById(MYREACTIONS_ID + "fingerButton").click();
driver.findElementById(MYREACTIONS_ID + "imageIndexFinger").click();
driver.findElementById(MYREACTIONS_ID + "startButton").click();
WebElement tapButton = driver.findElementById(MYREACTIONS_ID + "imageTapButton");
int x = tapButton.getLocation().x + 50;
int y = tapButton.getLocation().y + 50;
for (int i = 0; i < 350; i++) {
driver.tap(1, x, y, 1);
}
String result = driver.findElementById(MYREACTIONS_ID + "resultsFasterClicker").getText();
assertEquals(result, "350");
}
}
Open Android simulator. Or create a new Android simulator. Or connect Your Android test device. Do not forget to enable developer mode on Your real device.
Open Appium desktop app and start it. Wait few seconds before Appium is ready to use. Run the test with JUnit.
This is it. Just several simple steps to run the simplest scenario with Appium.
I hope that now You’re confident with mobile automation and You know how to start with it.
Most of engineers started to learn mobile automation with Appium. This is the most popular framework for mobile automation testing and I think that everybody agree with this. But sometimes it’s not enough to have only Appium, especially if we want to test native Android application with only WebView container inside. Appium cannot recognise elements in WebView container.
What to do in this case? Some test engineers decided to postpone with automation. But in reality this automation is even much easier than testing of native application with native controls.
How WebView container works? It’s loading mobile version of web site into custom WebView form. It means that we can easy inspect elements with Chrome or Firefox inspector.
But how to say Appium to search for elements exactly in this WebView? Many of You guys heard that need to switch context. But what if You run Appium inspector and You see only 1 context called NATIVE_APP ? In this case You need to switch Appium to Selendroid mode. For UI Appium inspector this is here:
But if we want to run the tests in Selendroid mode, we need to specify capability “automationName”: “Selendroid”.
After this You will see that You have more contexts than only NATIVE_APP, but also 1 or more WEBVIEW contexts. The next step is switching to correct context (for example):
driver.context("WEBVIEW_0").switchTo();
And that’s all. Now You can easy use the same methods like for Selenium WebDriver to navigate and click.
Also, You can use method .get(“url”) to easy navigate to any pages without clicking on UI.
Hope it will help You to solve some issues and start automation of hybrid apps.
In the previous lesson You learned how to develop simple verification methods, how to decorate them correctly to receive pretty results in case of failures. Today we will review very interesting and very useful topic regarding advanced verifications and how to implement it with Automotion.
So, we used to have the standard verifications, when we verify only that element is displayed or not. But usually we don’t do any validations that elements are aligned properly on the page. Nowadays we have desktop and mobile web application with responsive design. And correct alignment of elements on the page is super important part of business.
We want to make sure that tabs “TOP”, “NEWEST” and “MY PHOTOS” have correct order and they are aligned properly. And also we need to validate that footer is placed somewhere under top header.
The second thing that we want to verify – that this home page has correct localisation language and the whole text is really in English. Not latino, but really in English.
You will find everything in attached video. Wish You nice watching!
Amazing!
Now we can cover our test suite that require to have some UI/UX and linguistic skills!
In this lesson You’ve learned very interesting things of how to make verification of proper alignment and orders of elements on the page and how to validate that page has correct localisation. Hope this information will help You in Your automation.
Do not miss the next lesson. We will review the implementation of action classes and some advanced usage of Automotion.
Today we will review one of the most important part of automation framework – verifications. Obviously that if our tests verify nothing – they are useless. So, this lesson will give You an understanding of how to create classes for verifications and how to customise them to have nice test results.
Some engineers likes to keep verifications in the body of unit tests, some of them would like to keep it in the same class with page objects. I would prefer to create separate package “verifications” and for each of our page object class create appropriate class for verifications.
Sometimes we need to have base class for verification to keep different methods for base verifications in this class.
Each of our verifications methods will return string with error messages if such were detected during verification.
So, let’s start to implement our first verification class.
Have a nice watching of video lesson!
Well, in this lesson You’ve learned how to create verifications, how to manage the readability of results and tests. It is super important part in creation of the framework for automation testing.
In the next lesson I will show You how to work with advanced verifications, when You want to verify language of the web page, or if elements are aligned correctly, etc. This information You will find in my next video.
Today we will have a short lesson and I’m gonna show You one of the ways of how to use Page Object (simple example) with Automotion. There are many different approaches in usage of Page Object and it is hard to say what is better and what is less good. We will use Automotion library to define web elements with fluent waiters correctly. The example that will be showed is based on the web-site https://www.facey.top. We will add 5 elements into our HomePage class. There are: Logo, tabs “NEWEST”, “TOP”, “MY” and footer.
First of all we will create new package “pages” in directory “src/main/java”. Correct naming of the packages is not some strict rule, but this is a part of a clean code that is very important for test maintenance. After creating package “pages” let’s create Java class “HomePage”. All next steps and tricks You can find on the video.
Have a nice watching!
So, huh! You know already how to create new Maven project, add Cucumber scenario, extend scenario, create first steps for Selenium tests, what is pattern Page Object and how to use it. Now You have enough skills to create some simple automation testing solution. But this is only beginning. And in the next lessons You will find much more interesting information about advanced automation testing.
Learn how to create advanced verifications in the next lesson.
