1. The document discusses approaches for building a scalable test automation framework including choosing technologies, dealing with common pain points, and publishing test results through continuous integration. 2. Some challenges mentioned are browser crashes during testing, locating elements strategies, and simulating gestures on mobile apps. 3. The presentation recommends practices like using a headless browser for remote testing, monitoring processes, taking screenshots, and publishing test results and status to help debug issues and make release decisions.

1. Can we have it all !
Selenium- Soup for all
Approaching scalable test automation framework
SeConf UK Nov, 2016
Pooja Shah

2. iPod
iPhone
iPad
iPaid

3. 3

4. We shall not pass

6. 6

7. •Choice of Tech Stack
•Pain Points
•Work Around
•Sell your bugs

8. Ideal World ~ way towards Agility

9. Are Unit Test & Integration test Enough?
Frequent UI changes
Backend Releases affects mobile apps ?
API parameters changed
Unreachable code in production mode
HTML templates being passed

10. a Omni-channel product?
10

11. Pain Points:
1. browser die/server crash/inspector crash/simulator crash/
stuck
2. locating strategy
3. time consuming to test the test
4. Simulating gestures
5. same works 1st time but doesn’t work next time

13. 13
Sample XML
<root>
<popup>
<node1 name=“Cancel”/>
<node2 name=“Sign Up”/>
<popup>
………………….
………………………….
<popup>
<node1 name=“Cancel”/>
<node2 name=“Sign Up”/>
<popup>
<root>

14. 14

15. Trigger & publish test results ?
Sell your bugs with CI !
Accessibility
Transparency
Every possible feedback data at one point

16. From local script to remote jenkins
Issue
Flaky tests on remote
To do’s to debug
logs
screenshots
understand processes
Solution
Xvfb 1400x1200x16 Dimension dimension = new Dimension(1224,800);
Monit

17. Release Status Analyser
Tests list
Tests status (Pass/Fail)
Developers responsible
Release Go/NoGo call quickly
Release version to Revert Back to avoid the Fix bugs in
production

18. Fixing
bugs
in
Production

19. http://p00j4.github.io/

20. RSA - http://p00j4.github.io/

21. DDD (Debug Driven Development)
~ Oren Rubin
Test Code be of production quality
Appropriate Design pattern
Units (Say no to Large Tests)
Say no to “static” unless intended
Proper logging
Take screenshots as much as possible
Automated everything? way to start -> publish results in RSA

22. Demo Project: https://github.com/p00j4/scalable-framework
Selenium: http://www.seleniumhq.org/
Appium: http://appium.io/
Jenkins: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial
IRC: #selenium #jenkins #appium
References & Credits

23. Thank You!
http://meettheqagirl.blogspot.in
@p00j4shah
http://p00j4.github.io