The Future of Selenium for mobile web and native apps

Transcript

1. The future of Selenium testing for mobile web and native apps
2. Hi. I’m JASON CARR. I work at sauce LABS.
3. @maudineormsby
5. I’m a developer and contributor to SELENIUM and APPIUM
6. Context
7. For mobile web, Web Driver
8. Script Script Selenium Grid (optional) Selenium Grid (optional) iWebDriver.app
9. Script Script iWebDriver.app
10. iWebDriver.app from selenium import webdriver hub = ‘http://localhost:3001/wd/hub’ caps = webdriver.DesiredCapabilities.IPHONE driver = webdriver.Remote(hub, caps) from selenium import webdriver hub = ‘http://localhost:3001/wd/hub’ caps = webdriver.DesiredCapabilities.IPHONE driver = webdriver.Remote(hub, caps)
12. Limitations
13. iframes
14. driver.quit()
15. Alert handling
16. Javascript
17. UIAutomation
18. “…a bit like being dropped off in a field somewhere with no map, tools or supplies and being told you need to build a house.” -Alex Vollmer
19. js js Instruments.app Instruments.app App
20. js js Instruments.app Instruments.app App CLIENT DEVICE
21. UI Automation only runs in Instruments.app
22. Tests have to be in Javascript
23. No realtime interaction with tests
24. Hard to reuse code
25. One test at a time
26. An aside: Android automation…
27. Monkey Runner
28. So what have we LEARNED SO FAR?
29. Two attempted approaches to automation
30. Script/ Framework Script/ Framework Screen Capture Screen Capture App CLIENT DEVICE
31. Hard to abstract
32. Very brittle
33. Hard to use with real devices
34. Hard to use with CI or parallelize
35. script script Client library Client library App CLIENT DEVICE
36. Requires code modification
37. Real devices are hard
38. New framework and new tests
39. The RIGHT WAY TO AUTOMATE IOS
40. Remember the testing pyramid
42. Are you writing unit tests for apps? It’s not that hard!
43. Test your views appropriately
44. For UIWebViews use iWebDriver
45. Yes, yes, but NOW WHAT?
46. Code reuse is good.
47. Realtime interaction
48. Integrate with existing automation
49. Parallel tests and real devices
50. That sounds great, BUT HOW?
51. APPIUM
52. Open Source Can be extended
53. Uses webdriver API Runs with off-the-shelf client libraries Language agnostic
54. Real time Interact with js interpreter or client
55. Real devices
56. Works in parallel (architecturally)
57. No code modification
58. test script test script Instruments.app Instruments.app App CLIENT DEVICE Appium Server Appium Server
59. Easy to get started
60. Clone Appium
61. pip install bottle
62. python server.py /path/to/my.app
63. from selenium import webdriver command_url = “http://localhost:4723/wd/hub” iphone = webdriver.DesiredCapabilities.IPHONE driver = webdriver.Remote(command_url, iphone) fields = driver.find_elements_by_tag_name('textField’) fields[0].send_keys(3) fields[1].send_keys(4) buttons = driver.find_elements_by_tag_name('button’) buttons[0].click()
64. DEMO
65. Doesn’t support execute_script() …yet. More on this later.
66. 1 Second delay between commands UI Automation limitation
67. Still uses UIAutomation ‘Accessibility’ is important
68. WHERE DO WE GO FROM HERE?
69. WebKit remote debugging protocol
70. Drive mobile safari
71. Drive desktop safari
72. Drive chrome on android!
73. Android RC
74. Questions? Thank you!
75. Resources Appium Github Repo: http://goo.gl/4E5F0 Dan Cuellar’s talk on Appium: http://goo.gl/qgLha François Reynaud on ios-driver: http://goo.gl/pzn75 Simon Stewart’s blog on mobile testing: http://goo.gl/8wl8j