Dennis Soh Article authored by Valéria Lelli Leitão Dantas Fabiana Gomes Marinho Aline Luiza da Costa Rossana M C Andrade Background Explosion of mobile technology 60 million smartphone ID: 344975
Download Presentation The PPT/PDF document "Testing Requirements for Mobile Applicat..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Testing Requirements for Mobile Applications
Dennis SohArticle authored by: Valéria Lelli Leitão Dantas, Fabiana Gomes Marinho, Aline Luiza da Costa, Rossana M. C. AndradeSlide2
Background
Explosion of mobile technology60 million smartphone users in US in 2009Expected to grow to 142 million by end of 2011iPad, other tablets growing in popularitySlide3
Background
Android, iOS, Palm WebOS, Windows 7 among mobile OSesEach has unique properties, including unique development environment, programming language support, etc.Slide4
Problems
Testing software on mobile devices has unique challengesThese must be considered early in developmentSlide5
Key factors
Mobile ContextEnvironment limitations; e.g. screen, (lack of) keyboard, etc.Mobile UserOn-the-go; not sitting at a deskMobile ApplicationDifferent aspects of the device that the software can interact with; network operator, I/O interfaces, etc.Slide6
Any test plan needs to consider these factors!Slide7
Research methodology
2 questionnaires, sent to 40 professionals at 15 companiesProfessionals worked on >1 mobile app, >3 months experience in mobile app dev.Questionnaire 1: for developersQuestionnaire 2: for QASlide8
Proposed Testing RequirementsSlide9
Testing Requirements
Development process model must focus on testing processIncremental process most popular; used by 70% of professionals surveyedTest process should consider mobile context; 85% of professionals not using test process designed for mobileSlide10
Testing Requirements
Mobile applications must be tested on both emulator and real devices
EmulatorMobile Device
Functionality
Device variations
(keyboard, screen size, etc.)
Usability issues,
design
Usability
issues specific to device
User behavior
Performance, resources, real-world problemsSlide11
Testing Requirements
Test reports must document details about the test environment (emulator/device, device model, OS version, etc.)Testers must verify that application does not harm any existing applicationsInterruptions (e.g. someone’s calling you) must be handled appropriatelySlide12
Testing Requirements
Applications must be tested according to their targeted mobile context limitationsMemory, CPU, screen size/resolution, power, etc.Test process must differentiate between features to be tested in controlled environment and features to be tested “in the field.”Slide13
Testing Requirements
Usability testing specific to mobile applications must be included in testing phase56% of professionals perform usability testing, only 18% do so in fieldMobile user must have a clear sense of the state of the application.What have you already done? What can you do now? Can you undo actions?Slide14
Testing Requirements
Application must support change in device orientationPortrait/landscape formatApplication must ask for permission before making connectionsWhat if user doesn’t have unlimited data? Lawsuit!Slide15
Testing Requirements
UI layout must be appropriate for mobile devicesMinimize scrolling, appropriate contrast in background/text, appropriate text size, etc.Important/irreversible actions should require confirmationEasy for user to make mistakes due to screen size/imprecise inputSlide16
Testing Requirements
Sound (if present) should be useful and be integrated with device’s sound controlsButtons should act in manner appropriate to the deviceE.g. don’t bind the “exit” or “back” key to positive actions such as select and “OK”Slide17
And the Survey Says…
No real consensus on the “right” way to test mobileVery limited adoption of automated test tools (only 10% of professionals surveyed)Slide18
Testing the Tests
Researchers applied test requirements to a mobile shopping appTest requirements were found to be beneficial in highlighting areas of concern specific to mobile appsSlide19
Conclusion
Testing for mobile has unique challengesVastly different spread in hardware configsMobilityHardware constraintsRecent proliferation of mobile devices -> lack of consensus regarding development
Companies are “winging it”Slide20
Conclusion
Proposed requirements offer a “starting point”No comparison point because this is presumed to be better than “winging it”In future..Requirements should be refined and prioritizedRequirements specific to certain categories of applications should be defined