Сайт конференції: http://mdday.lviv.ua/ Наша facebook сторінка: https://www.facebook.com/startuplviv Наша linkedin сторінка: http://www.linkedin.com/groups/Mobile-Dev-UA-5186442 Ми на youtube: http://www.youtube.com/StartupLviv

3. Constant UI changes
Functionality changes
HOW OFTEN THE APPLICATION IS MODIFIED?
HOW IS IT MODIFIED?

4. We want to save money
We want to decrease release cycle
We have corporate goal
… We have additional budget – we need a
hole for it!
WHY DO YOU WANT TO AUTOMATE?

5. We have solid junior manual tester
We already have purchased super duper tool, it
will solve all the issues even before it is used.
Consider the fact you need a serious first
investment
WHAT IS THE EXPERTISE?

7. • We have Level of Services
• OMG, we have unit tests!
• We will stick to the UI. It’s logical!
WHERE WE ARE WE GOING TO AUTOMATE?

8. • Define high priority scenarios
• Smoke
• High priority functional tests
• Decrease number of steps
• Calculate ROI
• Yep, it really helps!
WHAT ARE WE GOING TO AUTOMATE?

9. Are we able to modify the system under
test?
How are we going to run the tests?
Who will be responsible for automation?
DEFINE YOUR SYSTEM UNDER TEST

11. Device
 Original
 Jailbreak/Root
Physically
 Simulator
 Device – cable
 Wi-Fi
 Device cloud
Logically
 Native
 Built- in agent (instrumentation)
HOW THE TOOL WILL INTERACT WITH THE SUT?

12. INTERACTION LOGICALLY - NATIVE

13. INTERACTION – BUILT IN AGENTS

14. Tests development/run platform?
Macs
Windows
Codding Language
Java Script
Java
.NET
Python
…
WHAT IS PREFERRED SCRIPT IMPLEMENTATION
TECHNOLOGY?

15. Failure rate
20-30% failure rate only because of the tool
issues
Different builds for market and test
INSTRUMENTATION ISSUES

16. Native:
 UI Automation
WiFi / Cable based (through instrumented
agents):
 Ranorex
 Monkey Talk
 Telerik Studio
 Silk mobile
 …
Interesting approaches
 See Test (through iOS bridge)
 Appium
IOS TOOLS – BASED ON ACCESSIBILITY

17. Different UI experience
Different flows
Different implementation teams
Different ways tools interact with the SUT
You expect it to work???
MOBILE MULTIPLATFORM TESTS

18. Resources
 Manual Tester
 No customer support/budget
SUT
 No/Rare changes in UI
Scope
 Some repetitive actions
 Smoke tests
Selection
 UI Automation
USE CASE 1

19. Resources
 Senior automation tester
 Customer support
 Huge budget
SUT
 No/Rare changes in UI
 Several platforms
Scope
 Complete test suite
Selection
 Silk Mobile
USE CASE 2

20. Resources
 Senior automation tester
 Customer support
 Budget under consideration
 .NET/Windows is preferred platform
SUT
 No/Rare changes in UI
 Hybrid iOS
Scope
 Complete test suite (65 steps per TC)
Selection
 Appium
USE CASE 3

21. iOS Appium does not work from Win!
Selenium Web Driver – API in almost any
language
Deployment topology – that makes the magic!
BUT…

22. Gestures support
Application reset after each test strategy
Device diversity
Application accessibility
CI integration
Need of extra permissions
OS support (Min < target < Max)
DON’T FORGET TO CHECK…

23. QUESTIONS?