Posted on December 8, 2015
How should you test your app? — 7 easy steps
If we want our client to be satisfied with the product we are developing for him, there should be a good communication between our software house and him or her. Sometimes (in fact very often) even the most precisely discussed product will look a little different in the client’s and developer’s imaginations. And what’s the most important — even the best developers make mistakes.
Therefore overseeing a developing product and reporting errors is very important, when we talk about future results. It looks like this in every unit production, and nothing changes in when it comes to mobile apps. For clients, who want to check if the version of an app they get is exactly what they need (satisfying all their needs), I will try to show how to test it in few easy steps.
- Basic task
It looks very basic at first, but precisely stating „what our product will do?” is one of the key steps in the beginning. Just ask yourself — what is my app for and what are its functionalities? Precisely determining how the process (or processes) in an app will work, should force a structure and main functionalities on it. If the main goals are not there, further testing seems pointless.
❏ Make sure, that your app meets all its main tasks
2. Distribution of content
For the app to be comfortable and user-friendly, its content should be appropriately distributed. It’s very important, to try and see things from the user’s point of view. He/she should relatively easy find the logic of our site. There should not be too much content, but dividing everything into categories is also not a good idea — it will make our site counterintuitive in use.
❏ Check if you are really in the middle of the app
- Important additional functionalities
Adding more functionalities to the app’s main ones is a very good idea. It might be, for example, comparing products in an online shop, setting up an accounts or search option. It’s very important for those additional functionalities to be really useful, in the other case they will make the app’s overall grade worse, rather than better.
❏ Precisely test all the additional functionalities
- Graphics and app’s design
Even the best divided content can be badly placed on the site. It is the deciding factor when it comes to comfortability and speed of our product’s usage — key factor for our potential clients. Everything should be at hand and according to known patterns of page navigation. Additionally used graphics and icons should hint their functionalities, rather than just distract the user’s attention.
❏ Is the content divided in good, functional way and easy to use?
If every subpage would be created in a different way, even a good content, divided in a clear and intuitive way, wouldn’t matter, because navigating through the subpages would be so hard. Therefore be consistent — create all the subpages in a similar way. Also allow your users to make mistakes and check if going back to the previous pages and navigating between categories is an easy task. You should also be consistent when it comes to colours used on your page.
❏ Check if your project is consistent and easy to use
You should also remember, that not everyone is viewing your page in the same circumstances. Every computer is different, has different operative system, various size screen, other web browsers can also change pretty much everything. And we didn’t even start talking about mobile devices. It’s good to check, if everyone will be able to view your site in the way you wish them to.
❏ Test your product on various devices, web browsers, versions etc.
For everything to work as planned, you have to be sure, that all the provided content is there and in the right place. All links have to connect with correct subpages, where the user will find what he or she needs. All texts, links, photos, addresses etc. connecting to social media, has to be on their places and work.
❏ Test your content — is it there and is it correct?
If you have already done all those things and found errors, write them along with links and all your doubts, make screens and send it all to person who is responsible for the project, or knows who direct it to. Constantly asking yourself (and other people engaged in this project) “Is it really how it should work?” is a very good practice. After correcting the mistakes, you have to test your product again — it’s very probable, that new errors will show up. In truth you have to repeat this process time and time again and don’t really believe that there are no more errors. If they are no more, you probably haven’t clicked in everything or missed some subpage/function. Although if after few cycles you can’t find any errors, let’s say that you did good job.
Basically, the tester’s role is to break up the app, find every possible weakness and check even the smallest details, so he won’t miss any mistakes. That’s the only way to make a really high-quality product.