QA Fest 2014. Ярослав Пернеровский. Appium - два в одном. рецепт приготовления коктейля из мобильных автотестов

Appium 2in1
Mobile tests cocktail recipe

Who?
Yaroslav
Pernerovskyy
 Test Automation Lead in
Global Logic
 Trainer in QA Factory
y.pernerovskyy
ypernerovskyy@qafactory.com.ua
www.linkedin.com/pub/yaroslav-pernerovsky/1/9b5/55

Why?
 Web application
 Selenium based test framework (Java)
 iOS and Android clients
 Reuse framework features for mobile
 Open Source (Free of charge)
 Easy setup and configuration
 Scalable and flexible

Appium Rules
 Test the same app you submit to the
marketplace
 Write your tests in any language, using any
framework
 Use a standard automation specification and
API
 Build a large and thriving open-source
community effort
http://appium.io/slate/en/master/?ruby#appium-philosophy

iOS
Android
Firefox OS
Test Script
JSON Wire
protocol
How it works
Native
automation
instruments
Remote Web
Driver
node.js
UiAutomator
Selendroid
Instruments
Marionette

 Native automation instruments
Android: UiAutomator (4.2), Selendroid (2.3)
iOS: UIAutomation
Firefox OS: Marionette
 Emulators/simulators and real devices
 Web Driver API
 Selenium Grid
 Ruby, Python, Java, JavaScript, PHP, C#...
 Documentation
 http://appium.io/
Features

Install
 npm install -g appium
 Appium.dmg
 Appium.exe
 https://bitbucket.org/appium/appium.app/downloads/

Command line
appium -a 192.168.10.11 -p 4723
--device-name "iPad Simulator" --force-ipad
--orientation LANDSCAPE --pre-launch
--app /products/testapp.app
--nodeconfig /appium/nodeconfig.json

Issues
 Stability issues
 Actions depends on platform
 Problems with accessing some elements
 iOS specific issues
Single app test
Hardware keys support
One emulator instance
xpath issue

Application types
Mobile Browser
Device APIs
Native App
0101010101
0101010101
0101010001
0011110101
0010011100
1010000001
<html>
<body>
<input type="button"
value=" + "
onclick="plus()">
<script
language="JavaScrip
t">
unction plus()
{
rezultat.value=znah_
1.value-(-
1)*znah_2.value;
}
</body>
</html>
Device APIs
Native Container
<html>
<body>
<input type="button"
value=" + "
onclick="plus()">
<script
language="JavaScrip
t">
unction plus()
{
rezultat.value=znah_
1.value

Web apps
 Similar layouts
 Same locators
 Absolutely the same tests can be executed
 Not require additional efforts

Native apps
 Different layout
 Different locators
 Platform specific UI elements
 Test cases should be specially designed
 Require additional efforts

Test environment
SVN
Jenkins
Web Firefox
Web Chrome
Mobile iOS
Mobile Android
……
Selenium
Grid
Chrome, FF
IE
Safari
adb
iPad simulator
iPhone simulator
Nexus 7
Nexus 5
Appiumreports

Selenium
Test framework overview
class Drivers
class Bindings
Page Objects
Page Objects
Page Objects
Page Objects
Tests
Tests
Tests
Tests
Global Configuration
Test data
loggers/db tools/service tools
etc.

Tests
 Test steps should be similar for both platforms
@Test (dataProvider = "Logins")
public void verify_Incorrect_Login(Map<String, String> testData){
loginScreen.verifyScreenLoaded();
loginScreen.submitLogin(testData.get("User"),testData.get("Password"));
loginScreen.verifyAndCloseErrorMessage(testData.get("Message"));
loginScreen.verifyScreenLoaded();
}

Page Objects
 Do not hardcode locators in Page objects
 Store it in external object
 Implement platform specific code
 Create bindings for platform specific actions

Page Object
public class LoginScreen extends Bindings {
public LoginScreen(Instance instance) {
super(instance);
initLocators();
}
private static String LoginScreenUserField;
private static String LoginScreenPasswordField;
private static String LoginScreenSubmitLoginBtn;
private static String LoginScreenErrorMsg;
private static String LoginScreenErrorMsgCloseBtn;
private void initLocators() {
LoginScreenUserField = locators.get("LoginScreenUserField");
LoginScreenPasswordField = locators.get("LoginScreenPasswordField");
LoginScreenSubmitLoginButton = locators.get("LoginScreenSubmitLoginButton");
LoginScreenErrorMsg = locators.get("LoginScreenErrorMsg");
LoginScreenErrorMsgCloseBtn = locators.get("LoginScreenErrorMsgCloseBtn");
}
...
...

Page Object
public void submitLogin(String login, String pass) {
typeKeys(LoginScreenUserField, login);
typeKeys(LoginScreenPasswordField, pass);
tap(LoginScreenSubmitLoginBtn);
}
public void verifyAndCloseErrorMessage(String Message) {
verifyElementPresent(LoginScreenErrorMsg);
assetEqual(getText(LoginScreenErrorMsg),Message);
if (instance.getPlatform().equals("ios"))
tap(LoginScreenErrorMsgCloseBtn);
else
clickBackBtn();
}

Locators
<?xml version='1.0' encoding='UTF-8'?>
<dataset>
<LOCATORNAME="LoginScreenUserField"
ANDROID="id=com.example.myapp:id/txtUser"
IOS="xpath=//window[1]/textfield[1]"/>
<LOCATORNAME="LoginScreenPasswordField"
ANDROID="id=com.example.myapp:id/txtPassword"
IOS="xpath=//window[1]/textfield[2]"/>
<LOCATORNAME="LoginScreenSubmitLoginButton"
ANDROID="name=Login "
IOS="name=Login"/>
<LOCATORNAME="LoginScreenErrorMsg"
ANDROID="id=com.example.myapp:id/errText"
IOS="xpath=//*/UIAPopover[contains(@name,'ErrorText')]"/>
<LOCATORNAME="LoginScreenErrorMsgCloseBtn"
IOS="name=Ok"/>
...
...

Summary
 WebDriver concept
 Cross platform
 Open Source
 Easy integration into existed frameworks
 It Works!
 Has issues
 But it works!
 With some additional efforts it is possible to execute
exactly the same tests on different platforms

QA Fest 2014. Ярослав Пернеровский. Appium - два в одном. рецепт приготовления коктейля из мобильных автотестов

More Related Content

What's hot

Viewers also liked

Similar to QA Fest 2014. Ярослав Пернеровский. Appium - два в одном. рецепт приготовления коктейля из мобильных автотестов

More from QAFest

Recently uploaded

QA Fest 2014. Ярослав Пернеровский. Appium - два в одном. рецепт приготовления коктейля из мобильных автотестов

Editor's Notes