Technical Mobile Testing - Risks, Issues and Experiences (EuroSTAR Mobile Deep Dive 2015)
2 likes1,689 views
The document discusses the challenges and risks associated with mobile testing, highlighting issues related to ergonomics, reporting, and device compatibility. It emphasizes the importance of accepting certain risks, improving processes, and utilizing workarounds to enhance testing efficiency. Additionally, it provides insights on tools and strategies for effective mobile testing and risk management.
Technical Mobile Testing - Risks, Issues and Experiences (EuroSTAR Mobile Deep Dive 2015)
- 1. Technical Mobile Tes.ng Risk, Issues and Experiences Alan Richardson - @eviltester EvilTester.com
- 2. What we learned when we tested mobile • Decisions we made • Pain we went through • What we did about it
- 4. What is hard about mobile tes@ng • Ergonomics • Observing • Repor.ng • Manipula.on
- 7. Pay aEen@on to pain to improve process • Gain some experience • Pay aBen.on to pain • Resolve pain to improve process • Status Quo != Dishwasher
- 8. Workarounds add risk • Adopt workaround, and mi.gate the risk • Communicate the risk • Accept risks through knowledge not fear (where possible) @eviltester
- 10. Mobile Technical and Risk Based Tes@ng • Our test approaches are oNen built around fear mi.ga.on – Lots and lots of devices – Because we don’t build for device compa.bility – We caveat for a subset of devices
- 12. Test Like Normal Users? • Default Browser? Dolphin, Chrome • LastPass Password Manager • Auto-Comple.on Off • Alterna.ve Keyboards – hacker’s Keyboard
- 14. Automa@ng Tac@cally • Screenshots for different screen sizes • Server based responses from mobile device headers • Not automated on device • Target Technical Risk Tac.cally
- 15. The challenge of observability • I hate tes.ng blind • Web Tes.ng more observable? • Proxies and Sniffers
- 17. Wifi Hoops and Roundabouts • Environmental Security • Tes.ng on wi-fi • Laptop Hotspots • Wireshark for na.ve via wi-fi hotspot
- 18. Proxy Benefits • Isolate device from server • Feed in new JS and CSS prior to release • Trigger error situa.ons on device without messing with server • Mul.ple scenarios configured by data fed to device by proxy
- 20. Cheap Ergonomic Solu@ons • Tablet stands • Stylus • Keyboards • Risk? – Fear mi.ga.on, use phone too – Even though this is built in OS func.onality
- 24. Screenshots from phone to desktop • AirPlay • VNC • Evernote • Dropbox • Email • Each tool adds risk?
- 26. Non-Technical Risks • Phones go walking • Start with secure library system • End up with cardboard box filled with devices
- 27. Lessons Learned • Don’t bring in your own kit • Never lend your kit • Buy 2nd hand/refurbished kit
- 29. List of how to test on each device • Each device is different • List the ‘shortcuts’ and lessons learned – How to take a screenshot – What tools to use
- 30. Future is geTng beEer • AirPlay • Chromecast • Miracast • Remote debug • Bigger phones
- 31. Risk Management • Iden.fy • Mi.gate • Accept • Communicate
- 32. Final Notes • Tes.ng on device is a risk • Iden.fy Technical Risk – Target to reduce plakorm tes.ng scope • If we were really serious…