Functional Testing• Test the installation, login, search and other common features• Write test cases• Do exploratory testing• Execute test cases• Do some automation
Security Testing• Manual Penetration – Cross-Site Scripting, SQL Injection, Denial of Service, Buffer Overflow, And others• Static Security Testing – Confidentiality: app keeps your private data private? – Integrity: data from your app is trusted and verified? – Authentication: app verifies who you are in any way? – Authorization: app properly limit user privileges? – Availability: can any attacker take your app offline? – Non-Repudiation: any logs of events?• Dynamic Security Testing – Search your active code for XSS, SQL and other common attacks – Cross-Site Scripting, SQL Injection, Denial of Service, Buffer Overflow – Inspect directories, leftover source code and resource files to find hidden username/passwords, SQL strings, ODBC connectors and other sensitive information.
Load & Performance Testing• Ensure that your mobile application is prepared for peak usage periods with a prepared load & performance services.• Live Load: talk to your employees to test the application on theirs/company phones first• Simulated Load: use simulated load testing tools to create thousands of real browser sessions (in case of a web app) to provide you with a complete snapshot of your web application’s performance• Hybrid Load: combine both testers with automated tools.
Localization Testing• Verification of context and accuracy for the localized mobile application• Validate translation twice with contracted translators• Full L10N Testing: – Content: static & dynamic – Dates: December 1 or 1 December – Characters: different sets of characters (French, Dutch, Romanian, Japanese, Mandarin, etc) – Postal Codes: only digits, or digits + letters – Phone numbers: different formats – Direction: rtl for exemple
Usability Testing• Test the usability of your mobile application• Is one – if not the —most vital task for a startup planning to launch a mobile application• Usability ideas to get started: – Page Layout: Ask your users to evaluate the overall effectiveness of the page layout. Are they instinctively drawn to your application’s main features, or are they directed elsewhere? Also, are they required to scan/scroll for any important features? In short, the layout might seem intuitive to you, but that’s probably because you designed it! Therefore, a fresh set of eyes is a must. – Color Schemes: This can include an evaluation of the use of colors in the background, text, links, icons, buttons and other aspects of your mobile app. – Findability: When conducting your user tests, give them a set of 4-5 items to find. This can include Help, About, Instructions, Search or others. This will help you determine your application’s level of accessibility. Remember, mobile users have far less patience than web users, so these items need to be placed in the best spot possible. Find out where that is. – Localization: If your application is going to be translated into other languages (or made available in non-English speaking markets), you’ll want to make sure that your app is consistent in terms of text, messages and symbols (e.g. dollar signs).