TEST THE RISK!

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

Testing is a group of activities which aim to make an application better by finding drawbacks. This explanation is not enough for successful testing result because every activities like checking, control, inspection, supervision or something apparently seen as testing activity do not fully accomplish what testing can do. In this post, I want to give some informations about the differences between testing and something such as checking which non-testing-knowledge people may see them as same.  First of all, let's look at the definition of testing by IEEE standard documentation IEEE - 829.1983 , this documentation sets the basics of testing and thereafter ISEB and ISTQB have used this standard for improving their software testing base. Definition of the software testing by IEEE is as follows, as you can see it in this reference : "Software testing is the process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs