A very big thank you to Michael Palotas from Grid Fusion & eBay International for taking the time and effort to travel across the globe to present at the Australian Test Managers Forum 2014. If you would like any information on TMF please email tmf@kjross.com.au
23. RISK & STRATEGIES
Hotfixes are difficult and expensive
Agile?
...yes...but...for mobile the goal should be to get it
right the first time
23
24. RISK & STRATEGIES
May shift back to waterfall
(waterfall is not that bad)
Difficult to get (mobile) experienced people
Need to grow capabilities in-house
24
25. RISK & STRATEGIES
No automation in most places today
No continous integration / continous delivery
25
26. RISK & STRATEGIES
DEVICE SELECTION
26
Be pragmatic
Focus on where your money is coming from
Forget the “Long Tail”
27. RISK & STRATEGIES
Multi code base
Many devices
Device / OS management
Simulator vs. real devices
27
32. GENERAL EXPERIENCES WITH THE CLOUD
No dedicated devices
Or no devices at all
Device management
Your company firewall...
Trust issues
Slow(er)
No in-house knowledge
Not onsite
It is a bit like outsourcing
$ in the beginning
$$$$$$ when you are scaling
32
35. CROWD TESTING – WHAT USUALLY WORKS?
Fresh set of eyes
Access to many regions, devices, OS
combinations
(at least theoretically)
Lots of issues reported
Relatively low cost
35
36. CROWD TESTING – CHALLENGES
Significant ramp up required for testers
Low bug quality
You don’t know who is on the other end...
People in mature markets won’t work for 5$ / bug
Only access to production environment
QA system access very difficult
Legal implications, NDAs etc.
No development resources to fix the bugs
36
49. AUTOMATION IS GOOD…BUT
Tools help, but tools don’t test
Manual testing is equally important
Manual (exploratory) and automated testing complement each other
49
Automation
Manual
50. WHY IS E2E TESTING SO IMPORTANT?
Because it is the most difficult way to test
Because our users use our products End2End
Because you can verify that the whole system
works together
50
51. PERSONAL THOUGHTS ON AUTOMATION
Manual testing is still very important
E2E tests are expensive, so keep them to the minimum Automation is software development
Be careful with record & playback tools
Automate the repetitive tasks (regression)
Build testability into your product
ROI...
More at http://gridfusion.net/thoughtsonautomation.html
51
53. MOBILE TEST AUTOMATION
Not as mature as web automation
Immature tools market
Tools are usually platform specific
Multi code base
Need to understand the underlying architecture
much more than for the web
Need people who can code well
53
59. ANDROID VS. IOS
Android: lots of variations, versions, vendors
Android: open source (sort of)
iOS: easy to update
iOS: everything comes from one vendor
iOS: not exactly open source J
59
60. SAMPLE MOBILE AUTOMATION
REQUIREMENTS
Use the same approach and infrastructure as web
Business is borderless à test automation needs to be as well
Aim for REAL E2E test automation
Use the Load Balancer / Resource Management Features of Selenium Grid
Manage multiple applications / versions / languages
No modification of mobile app
No modification of mobile device
Mobile App Runtime Inspection Support
Hybrid app support
Support for emulator + real device
Integration into CI system
60
61. SAME AUTOMATION CODE BETWEEN
PLATFORMS?
Sounds good first
but
Most apps are different between platforms
Different element locator strategy
Do reuse the helper functions
61
62. MOBILE AUTOMATION
IOS / ANDROID DIFFERENCES
iOS has no IDs à harder to automate
iOS relies on xcode
Android is open source
Android: ID support
62
66. WHAT ABOUT BDD / ATDD?
I have seen it working
Required to close the loop
Removed complexity
(while adding it at the same time)
Have you ever seen a product owner test?
66
69. SELENIUM – WHAT IS IT?
Web testing tool
Highly successful open source project Stable
Protocol describing the user interactions
Supports most browser implementations Support
for most common programming languages
69
70. SELENIUM – WHAT IT IS NOT
a drag & drop tool
a network testing / monitoring tool
a performance testing tool
a reporting tool
a testcase management tool
70
74. SCALING USING SELENIUM GRID
74
Client
serverGRID HubClient
CI
server
server
server
server
server
server
75. 75
Implements the JSON Wire Protocol (so it is fully compatible with Selenium)
Runs on emulators and devices
Can be run as a node in Selenium Grid
Support for localized native apps (1 test for all locales)
No need to change the AUT
No need to jailbreak the device
76. 76
Hybrid support
Different locator types are supported to find elements
Gestures are supported: Advanced User Interactions API
Hot plugging
It can be integrated as a node into the Selenium Grid for scaling and parallel testing
Android target API support from 2.3.3 to 4.3 (latest)
Built in Inspector to simplify test case development.
77. REPORTING
Invest into proper reporting
Easy analysis of the reports is crucial
Selenium does no reporting
TestNG or JUnit are responsible for reporting
100% customizable reports (i.e. different reporting levels,
PDF, HTML, Email, SMS etc...)
Hooks into test case management tools
77