In order to be successful at mobile app testing, testers need to be up to date with the latest in the mobile world. We have gathered four articles looking at what’s happening in the mobile application environment today and how to approach testing from a tester’s perspective.
Josh Michaels is an independent software developer who makes apps for the iPad, iPhone, and Mac under the company name Jetson Creative. In the interview, Josh discusses mobile development, testing aggressively, and keeping users happy.
Michaels answers how he tests his mobile apps:
JM: The first is that as I build I test aggressively, meaning that I try to not leave a feature until I’ve really just fully evaluated it. Because I’m writing the code and testing it, I’m able to really think concretely about the testing matrix and where there’s likely to be problems and where there isn’t likely to be problems. I try as aggressively as I can when I build a feature to right then test it as thoroughly as I possibly can as one individual.
Now, the challenge is that very often I’ll release this stuff and people use it in ways that I don’t even think about. Maybe they’ll set a couple of settings and I’m like why would you ever want to setting A this way but setting B and C this way? Sure enough people come up with a reason to do it and that’s where I can’t test it all because there’s going to be lots of different ways to set things up that are going to be ways that I don’t even think of and that’s where I really depend upon the fans and customers who really love the product who function as beta-testing group.
Like any application testing, it is important to go through the requirements in depth and rectify the requirement bugs at the right time. If you are not getting requirements properly, just communicate with your client or lead about which information you will be requiring in order to work on Test Scenarios and Test Cases around it. If there are many requirements which are decided on the go, like in the client calls or in the meetings, then write it down and start working on the various scenarios around them.
Make sure to analyze the requirements keeping mobile factors in consideration as well. For e.g. if the requirements is “mobile app download any media” then you should make sure to ask the following:
- What kinds of media files are going to be supported
- If download is going to be on SD Card or internal memory
- What if SD card will not be available
- What if user changes the SD Card
The article continues to look at the variety of requirements your client might ask you like UI mock ups, competitors application analysis and more.
The mobile device market, Smartphones, Tablets, PDAs etc., is growing dynamically making the mobile application developers strive to deliver most robust, scalable applications with quality assurance. Every device platform creates a unique testing environment challenging the mobile application developers to follow different testing strategies. Here we shall see how different types of testing approaches can be taken up for a variety of mobile platforms.
Numerous different mobile platforms available for mobile applications to name a few:
- Apple’s iOS
- Google’s Android
- Nokia’s Symbian, Maemo and MeeGo
- Palm/HP’s WebOS
- Samsung’s Bada
- RIM’s BlackBerry OS., and many more.
As mentioned, every platform needs a different testing approach. A combination of manual and automation testing can be done for an effective outcome.
Read the rest of the article for the different types of manual testing for the mobile environment.
With ever-increasing ubiquity of mobile devices, the marketplaces have seen an exponential increase in number of applications in the last few years. No wonder the word “app’’, which was referred to only in very technical contexts a few years ago, has found its place in official English dictionary now.
While a tester needs to apply the same analytical approach to test a mobile application, at the same time it is a bit more challenging as compared to testing a web application.
Some of the challenges in testing mobile applications are as follows:
- The biggest challenge when it comes to mobile application testing is the plethora of devices spread across different platforms. Obviously, it is not feasible to test your app on each and every available device which means you have to strategically choose a few physical devices.
- Different platform testing: In the case of native app, it goes without saying that it will need dedicated testing effort on all platforms for which it is developed. It gets a bit tricky in the case of HTML5 based hybrid applications. While the code remains the same, lot of factors come into play on different platforms.