Uploaded byStephen Janaway
An Introduction To Mobile Software Testing
This document is an introduction to mobile software testing presented by Stephen Janaway. It discusses why mobile testing is important given the huge mobile market and users' dependence on well-functioning mobile devices and applications. It also covers what types of mobile testing exist, including hardware, network protocols, applications, and more. Finally, it encourages getting involved in mobile testing as the field is growing rapidly and testing mobile applications is an easy way to break into the industry.
An Introduction To Mobile Software Testing
- 1. An Introduction toMobile Software Testing Stephen Janaway Test Manager Net-a-Porter Group
- 2. Who am I? StephenJanaway • 12 years experience in mobile software testing. • Mobile devices • Mobile networks • Mobile applications • Have worked for companies such as Ericsson, Motorola and Nokia. • Currently at Net-a-Porter Group. • www.stephenjanaway.co.uk • @stephenjanaway
- 3. This Presentation • Whymobile testing? • What is mobile testing? • Hints, tips and techniques. • Why get involved?
- 4.
- 5.
- 6.
- 7. The mobile marketis huge
- 8. Mobile devices are •Smart Phones • Feature Phones • Tablets • E-readers • Big screens, small screens, touch screens and keypads.
- 9. Mobile devices aremuch more • Alarm Clocks • Maps • Link to loved ones • Hand held shops • Tickets • Music Players • Books • Games Players • Cameras • …… • These are key experiences. Imagine if they did not work?
- 10. My alarm didn’tgo off…
- 11.
- 12. Where were wemeeting?
- 13. Quality is notcurrently great • Many applications launch un-tested. • Phones launch with serious issues (remember the iPhone 4 death grip). • Android has security issues. • Users tolerate this….but for how long? • How can we improve this?
- 14. Different Sorts ofTesting • Hardware level: • Protocol/ Air Interface: • Applications • The software that you test could be in the hands of millions of people once you have finished. • Releasing a phone with bugs in it loses a company a huge amount of money. • The mobile world is a low margin, high volume game.
- 15. Native or Web? •Native app: – Specifically designed to run on a device. – Runs on device OS. – Testing needs to include download/ upgrade/ uninstall. – Typically needs to be adapted for different devices. • Mobile website: – All or some parts of the software are downloaded from the Web each time it is run. – Usually accessible from all Web-capable mobile devices. – HTML5 makes it increasingly difficult to separate web apps from native apps. – Testing needs to include different mobile browsers.
- 16. Interactions • While yourapplication runs, the phone is: – Talking to the network – Working out where you are – Maybe receiving calls, texts, Facebook and Twitter updates. • What happens when you have your application running, and then get a call, and a text, whilst uploading video to YouTube? Test for it and find out.
- 17. Performance • Mobile deviceshave limited memory and limited processing capacity. • It’s important to test how the devices work when stressed. • Test for memory leaks and general performance of the operating system and applications. • Think of battery life!!! • Think of how the application works when network performance is poor or on different speeds (2G/ 3G/ LTE/ Wifi).
- 18. Apps Stores • Testapp store submission and download/ install. • One estimate is that 70% of applications are submitted to apps stores without any formal testing have been conducted.
- 19. Security • Only afraction of smartphones and tablets are protected by security software • Big recent rise in malware and copy apps targeted at mobile devices. • Test for security issues. • Check browser security, cookies, etc. • Check application permissions.
- 20. Usability Matters • Youshould test for usability. • Usability could mean testing it on a panel of real users. • Usability is more important in the mobile world: – Smaller screen. – More difficult to interact with and typically used one handed. • Typical areas to focus upon are: – How easy is it to use the application? Do user ‘just get it’? – How is the look and feel? – Does the application or device feel fast?
- 21.
- 22. Where do Iget all the devices from? • Don’t use them at all – simulators or user agents. • Buy them. • Rent them. • Use a cloud based service (Perfecto Mobile, DeviceAnywhere).
- 23. Automation – theanswer? • Yes and No • More difficult on mobiles. • Many options: – Appium – iOS Driver – Robotium – Gorilla Logic (Monkey Talk) – Touch Test – Bespoke solutions….
- 24.
- 25. So… • Smartphone usageis increasing rapidly. • Users are more emotionally attached to their phones than they are to their PCs. • Testing applications is the easiest route into the industry. • A mobile test strategy should not merely be a copy of a desktop test strategy. • “Be proud, your work will soon be in the hands of millions”.
- 26. And two morethings… Net-a-Porter Are Hiring • Dev-in-Test – Java/ Ruby • Test Automation Analyst Mobile Training • Coming in early 2014
- 27. Stephen Janaway Test Manager Net-a-PorterGroup www.stephenjanaway.co.uk @stephenjanaway Questions?