First Checks for Mobile Application Testing

Mobile application testing world is differentiated from web application testing in terms of the power of the control. The definition control, how much things you can do when users install the application to their mobile devices. Think, if you store warnings in code and deliver them inside the application code, you can not manage it unless the users update the application.

For sustainable mobile application development, you should have the control of the applications as much as you can do. Therefore the architectural design of the application should be ready for this flexibility. In this post I want to share the most important and primary checks for mobile application testing.

Security First

Whatever you develop, you can not disregard the security of the users. If you have an open deep-link for critical information, it will one day be distinguished by some one. Critical actions, such as login, sign-up, credit card submit, should not be sent over get requests, they should be sent over post requests and the data should be sent over requests body not in the query string. 

Warnings and Messages

The application should be a gateway to your system.  Application is just another presentation layer as connecting your and you on mobile devices. If it tries to customise things on the presentation layer,  you will not handle when you want to change the messages or warnings. You can only try to release new version of application to market, and wishing your users update the application. Therefore if you want to take the power of the control, the application should directly present the information which is passing by the api, stored in the database. After that you can update the messages in the database, and the application presents the new messages.

Checking the Application Version

When your application goes to live,  users are starting to use it. After a while, you release many versions of application. Each versions should cumulatively adds new things to the application code. This could be some major features, fixes or some regulatory update so you will have version history. For a case, some versions may possible have mandatory update, there should be easy way to check the version of the application. If the application send its version at the starting, you can direct it mandatory update. Otherwise there is only way to understand the version of the application by waiting to receive the version specific requests. 


Popular posts from this blog

Testing WEB Sevices and Automating SOAP Services

Performance Testing on CI: Locust is running on Jenkins

Change Default Timeout and Wait Time of Capybara

Performance Testing on CI: Integration of Locust and Jenkins

Create an Alias for Interactive Console Work: Selenium and Capybara