Posts Tagged ‘Functional testing’
The answer seems obvious, or does it? After all, the application on a mobile device has the same functionality as the application on a standard desktop computer or laptop. Well, the difference is that mobile apps have to be tested for their non-functional aspects (such as usability) on mobile devices and not just primarily focused on functional testing.
There are a number of challenges that are a direct result of the unique features of mobile devices and wireless networks:
Mobile context – interaction between the users, applications and the surrounding environment that may distract user’s attention
- Connectivity – slow and unreliable wireless network connection with low bandwidth is a common hindrance for mobile applications
- Screen size – physical constraints of mobile devices, especially small screen sizes
Successful testers avoid overemphasis on functional correctness, and focus on the ways in which people might obtain value from a program — or have that value threatened. Being a tester, reporting bugs clearly in order to alert a developer is just as important as verifying functional correctness. Testers should possess good documentation skills in addition to their testing capabilities. There are several instances that I know of where a major bug was improperly documented and reported to the developer.
My post offers a clear example that demonstrates the importance of documenting bugs properly, which is taken from one of our own testing instances. We needed to perform functional testing on a new feature that had been introduced for a media site. After completing functional testing, we were supposed to perform a regression testing on the media site since release was scheduled on the same day.