available_updates

5 Lessons About Testing Mobile Apps You Can Learn From Other Apps’ Updates

The world of mobile is ever-changing and constantly revolutionizing, leaving mobile apps’ testing experts with a necessity to improve their skills almost on a daily basis to be always “up-to-date”.

If you try and ask such experts about the best way to always have upgraded skills in mobile testing, you are likely to come up with the following suggestions:

  • Reading best QA-related blogs
  • Following QA experts on Twitter and Facebook
  • Trying every single mobile testing tool everybody else is using
  • Learning new testing techniques to develop creative approach to mobile testing
  • Trying to break an app in some ways it’s not intended to be used, etc.

Which another beneficial way of skills improvement is rarely mentioned is using other apps from from different categories as much as possible in order to understand the way they were built and their intended vs. actual behavior.

To go even deeper as well as to simplify the task, it’s also a great idea to check those apps’ update texts. You won’t even have to bother with looking for apps to examine – you can just make it a rule to read about all the updates of the app every time you are going to install the new version of the app you are currently using. Those nerdy developers who are precise in the apps they are getting into while updating the app to the latest version, may actually be right about doing so. Because whenever they are reading the updates text, they learn about the bugs in the previous version which have been fixed and the new features that have been developed.

And this is a perfect way to learn some important things about mobile app testing, such as:

  1. You should test your app on different devices more carefully.

In those update texts you can often see that an app performed a force close on some devices when some option was called.

  1. Speed and reliability should be the priorities.

You can often see the “improved loading process” update on the list which indicates the importance of the app’s performance, especially for impatient users.

  1. Introducing widgets in the app requires additional testing.

From many fixes connected with mobile app widgets, it becomes clear that this is an area which requires a closer attention of mobile testers. Whenever you introduce a widget into your app, check if it really works, if it’s not freezing, if it’s not consuming battery too much, etc.

  1. Sign-in and payment features must be tested for exceptions.

Often there are bugs in business-critical features like sign-in or payment. You don’t want bugs in these to affect your users, like in some apps you can see on the Stores.

  1. Think twice before requiring certain permissions from your app’s users.

Another common problem you can see in the old version of an app which gets fixed in the new one is requiring many permissions which only reduce the chances the users will install the app. So don’t repeat this mistake and be wiser. Set only the minimum of required permissions.

These are certainly not the only lessons you can get from other apps’ updates, but they are enough to make you interested. By trying to reproduce the bugs described in updates you’ll be able to boost your mobile testing skills more still. Even if you are far from a fresher, looking up the apps’ updates is never pointless as they can give you many new ideas for better testing!

Tagged:


TestFort Blog

About TestFort Blog

TestFort blog is an official blog of TestFort QA Lab company and is dedicated to various QA and software testing issues.


no comments yet

Be the first to comment this post!

Would you like to share your thoughts?

Images are for demo purposes only and are properties of their respective owners.
Old Paper by ThunderThemes.net © 2017

×