In a team which is developing mobile apps for multiple platforms, it becomes extremely difficult to maintain multiple Automation codebases and frameworks to test the app. This becomes a bigger problem when the same team is churning out multiple flavours of the same app. What this showcases is how we have built an automation framework that tests 2 different flavours of an app along with using the same framework to test these apps across 3 different platforms. The session will also include the challenges we faced while moving from a purely Functional approach to writing code to an Object-oriented approach to structure our automation code. This will help other testing practitioners attending this session in building a robust automation framework with a very reliable and scalable codebase that can be extended beyond just one application/platform.

1. 1AUTOMATION
FRAMEWORK, 2 MOBILE
APPS, 3 PLATFORMS
Bhumika Srinivas
Lead Quality Analyst

2. ABOUT US
bhumikaiyengar@gmail.com
bhumika@thoughtworks.com
linkedin - bhumikaiyengar

3. What is
Test Automation?

4. Automation
-
A Safety Net

5. Why do we do
Test Automation?

6. QUICK FEEDBACK

7. What are we
testing?

8. Manual / Exploratory
UI
View
JavaScript
Integration
Unit
PLATFORMS SUPPORTED

9. 2 AIRLINE APPS

10. 10

11. How are we
testing?

12. TOOLS & METHODOLOGY
○ Page Object Pattern
○ Functional Tests and Visual Tests
○ Calabash & Watir-Webdriver as drivers
○ Code in Ruby
○ Harper for mocks
○ Nakal for Visual tests
○ Cucumber for english style scenarios (automation & manual)
○ Espresso for Android Integration Tests
○ XUnit for iOS Unit Tests
○ Go CI for CI/CD

13. CALABASH & CUCUMBER - HOW?

14. Traps we fell Into

15. CUP-CAKE ANTI-PATTERN

16. Web Service
View
JavaScript
Integration
Unit
Developers Test Pyramid QA Team Test Pyramid
DUAL TEST PYRAMID ANTI-PATTERN
Manual / Exploratory
UI
Web Service

17. Whoa! How did we
solve that problem

18. SOLUTIONS
Rewriting our automation Code
○ SWAT team
○ Functional to POP
○ Addition of Visual Tests
○ Fix library issues, upgrades
○ Imperative to Declarative scenarios - User
journeys instead of User scenarios

19. SOLUTIONS
Biggest Win - Visual Tests

20. SOLUTIONS
Optimising Test Runs - Running them in Parallel

21. SOLUTIONS
A Good CI Setup - Right Dependencies

22. SOLUTIONS
A Good CI Setup - Splitting tests based on what is being tested

23. SOLUTIONS
Additional Tools to help us improve code quality - Sonar

24. THANK YOU
bhumikaiyengar@gmail.com
bhumika@thoughtworks.com
linkedin - bhumikaiyengar