We are using a variety of automation tools in our project. Appium is one of them. Since Appium is now one of the most used open source automation tools for Mobile we like to share our 2 years of experience: When do we use Appium? How do we use it? What does our architecture look like? Where are the pitfalls? Simply put: How does Appium fare in our day to day life and would we use it again?

1. Appium @ Work
Vienna, 2016-10-04

2. 2

3. 3
What do we do with Appium?
automated
checks
unit tests
(for logic)
unit tests
(for screens)
end-to-end tests
user journeys
jUnit
XCTest
Espresso
snapshot test case
Appium (Java)
& jGiven
emu-/ simulator
mock dependencies
emulated & real
mock dependencies
real devices
full system stack
Checking Type Tools Environment
*the most
*the fewest

4. 4
useful
Reporting
sustainable
Architecture
Intents
How do we use Appium?

5. 5
How do we use Appium?
Runners
(tests run here)
Page Objects
(this is your app!)
Data Builder
(create test data)
utils
reporting
AndroidSpecifics
iOSRunner
AndroidRunner
iOSSpecifics
CloudRunner

6. 6
How do we use Appium?

7. 7
iOS scrolling
some bugs,
Webviews
Where is Appium torturing us?

8. 8
Where don‘t we use Appium (or any automation for that matter)?
testing checking
is Coupon
activated?
How does
bad
connectivity
feel?

9. 9
What else can we do with our automation code?
test
automation
Automation in
Testing

10. 10
Would we use it again?
maybe
Do I want to support
both plattforms?
Do I want to have control
outside of my App?
Do I want to integrate
clouds?
Do I get the App
delivered by a 3rd party?

11. 11
PAYBACK GmbH
Gehlen Marcel
Mobile Tester
@Marcel_Gehlen
Theresienhöhe 12
80339 München
Phone +49 (0) 89 997 41 – 0
info@Payback.net
PAYBACK.net | PAYBACK.de
HAD FUN?
€