The following post was written by mobile app tester Dom Wolf as part of uTest’s “Crash Courses” series. You can read similar posts in the uTest Forums (membership required).
Background: The release of the iPhone in 2007 introduced not only a new product, but also a new dichotomy to the world of software testing. The iPhone was the first mainstream phone to feature a touchscreen coupled with a 3G/Wi-Fi enabled web browser; two things that caused web developers to consider not only how their sites would appear, but also how they would be interacted with in such a different way.
Approximately one year after the launch of the iPhone, the iPhone SDK and App Store were introduced. The popularity of the iPhone at this point spurred many developers to submit applications at an unprecedented rate. Some apps were simple utilities, easily to develop and easy to test. Some, on the other hand, made use of many frameworks built within the newly introduced iOS and were incredibly complex. As the store’s popularity grew, Apple found itself on the receiving end of criticism over the content, and reliability of applications being submitted. The latter point is where we come in.
So there are two deliverables that are typically evaluated through uTest – native applications and mobile sites (this includes so-called web-apps, which are basically extensions to a mobile or web site). For the most part, the same test procedures can be applied to both types of deliverable, and this is what will be covered in this Crash Course. There may be some forms of testing which are deemed out of scope for a particular project you’re working on.
It’s paramount that you check the scope before you start testing and raising bugs. Not doing so could lead to having bugs rejected, which may affect your eligibility to take part in future releases. So, assuming that nothing is considered ‘out of scope’, we could include testing of the following: