Mobile Phone Testing: iPhone vs Android Testing

Mobile Phone Testing: iPhone vs  Android Testing


The fasting growing area within software testing is the mobile app domain. Applications developed for mobile platforms such as Apple's marketing leading iPhone and also the less popular Android platform are being tested using the same methodology that was used earlier for desktop and web based applications.

There are companies which spend tens of thousands of dollars for mobile app testing projects. This is not only due to the fact that the mobile domain is ever increasing and so companies are feeling the need to contribute, but also due to the sensitivity of data which is a critical factor in the success of any mobile app. People whose data gets stolen or robbed from mobile applications are very unlikely to give it another try, as the data can pertain to personal information with respect to the customer.
For iPhone and iPad applications, we find that the audience tends to be in the young 20s or early 30s. As iPhone applications are primarily related to multimedia, we expect that the graphics will be given a severe and thorough testing. The user in these kinds of applications is generally concerned with what he/she experiences on the screen, with respect to 'viewing pleasure'.

For android applications there is a certain level of 'maturity' or advancement which is also related to the category of audience which uses it. Android apps are commonly used by people who belong to the executive category, and so the applications tend to be more towards the business side of things. For example; business evaluation applications or CRM (customer relationship management), we find that even though they are available on almost all the platforms, they are most commonly used in the android applications. Also, since android apps have more stability to them (no disrespect to iPhone apps), the business people tend to be more comfortable using it. Also since android is open source it makes it that much easier and compatible to be employed for business purposes. Also, we find that the bulk of android applications, users will typically use them as they are easily transferred to other devices, its blue tooth compatibility is also a plus.

An interesting point to be noted, is that even though the platforms might be vastly different, for example the iPhone and Android platforms; the testing theory still remains the same. The overall picture is still the same, even though the domain has changed. The application flow has to be understood, the business requirements reviewed and the happy scenarios executed for the application, be it mobile domain or web domain or any other domain for that matter. There could be arguments that iPhone app testing is easier or iPad app testing is harder, or for that matter, Android app testing is easier but essentially they are different facets of the same domain. If we can understand and develop skills in web based testing it will also work in mobile apps testing.


Author: James S Clark
Source: Link

Comments

Post a Comment

Popular posts from this blog

What is LCSAJ Testing?

Image
LCSAJ testing requires a model of the source code which identifies control flow jumps (where control flow does not pass to a sequential statement). An LCSAJ (Linear Code Sequence and Jump) is defined by a triple, conventionally identified by line numbers in a source code listing: the start of the linear code sequence, the end of the linear code sequence, and the target line to which control flow is transferred. Test cases shall be designed to exercise LCSAJs. For each test case, the following shall be specified: - the input(s) to the component; - identification of the LCSAJ(s) to be executed by the test case; - the expected outcome of the test case.
Read more

ISEB-ISTQB Sample Exam Paper 12

Image
1. Which of the following statements contains the correct use of the terminology? a) a fault by a person may introduce an error into the software that may cause a failure in operation b) a failure by a person may introduce a fault into the software that may cause an error in operation c) an error made by a person may introduce a fault into the software that may cause a failure in operation d) an error made by a person may introduce a failure into the software that may cause a fault in operation e) a failure by a person may cause an error in the software that may cause a fault in operation 2.   A reliable system will be one that: a) is unlikely to be completed on schedule b) is unlikely to cause a failure c) is likely to be fault-free d) is likely to be liked by the users e) includes a minimum number of components 3.   Which of the following statements about ‘Integration Testing in the Small’ is false? a) It can combine all the components ...
Read more

What is State Transition Testing?

Image
State transition testing uses a model of the states the component may occupy, the transitions between those states, the events which cause those transitions, and the actions which may result from those transitions. The model shall comprise states, transitions, events, actions and their relationships.   The states of the model shall be disjoint, identifiable and finite in number.   Events cause transitions between states, and transitions can return to the same state where they began.   Events will be caused by inputs to the component, and actions in the state transition model may cause outputs from the component. The model will typically be represented as a state transition diagram, state transition model, or a state table. Test cases shall be designed to exercise transitions between states.   A test case may exercise any number of transitions.   For each test case, the following shall be specified: -   the starting state of the component  ...
Read more