Mobile App Testing

TYPES OF MOBILE APP TESTING

To address all the above technical aspects, the following types of testing are performed on Mobile applications.

Usability testing – To make sure that the mobile app is easy to use and provides a satisfactory user experience to the customers.

Compatibility testing – Testing of the application in different mobiles devices, browsers, screen sizes and OS versions according to the requirements.

Interface testing – Testing of menu options, buttons, bookmarks, history, settings, and navigation flow of the application.

Services testing – Testing the services of the application online and offline.

Low-level resource testing - Testing of memory usage, auto-deletion of temporary files, local database growing issues known as low-level resource testing.

Performance testing – Testing the performance of the application by changing the connection from 2G, 3G to WIFI, sharing the documents, battery consumption, etc.

Operational testing – Testing of backups and recovery plan if the battery goes down, or data loss while upgrading the application from the store.

Installation tests – Validation of the application by installing /uninstalling it on the devices.

Security Testing – Testing an application to validate if the information system protects data or not.

ReTest - Retesting is when you are testing a specific defect that has been marked or
tagged by the developers as ready for testing in the build in which you are working.

Regression Testing - Regression testing is when you are testing around specific areas of an application where defects have been fixed to ensure that no other issues have been introduced.

Smoke Testing - Smoke testing refers to a short series of tests that are executed to make sure that the build appears to be reasonably working the build appears to be functional.

Sanity Testing - Sanity testing is the same as smoke testing. There seem to be many terms used for smoke testing I've also heard the term acid testing. If a major part of the functionality is found to not be working for a smoke or sanity test, then the build is often turned back to development. Smoke testing doesn't prove everything is working but usually provides a sense that the build is good enough to begin testing in earnest.