Manual mobile testing is still a very commonly use testing practice exercised by most of QA engineers and testers. To make your manual mobile testing as effective as possible you want a testing structure. Without a structure you ’ ll be just clicking around, hope to regain a bug. With structured trial, you will be able to regain bugs and flaws methodically and you ’ ll be able to repeat the like test on multiple devices and to reproduce bugs if needed. That ’ s why we put together an ultimate checklist that will facilitate you structure your tests and make your manual mobile essay nearly infallible.

This guide will make you a perfect roving manual tester to render flawless mobile apps.

Download the free cheatsheet to organize your mobile testing at the end of the clause!

Manual Mobile Testing: The 7 prosperous rules!

Rule # 1 – Make a plan!

When get a new examination project there are many different thing that need to be sorted out. First of all, resolve which test cases should be tested manually and which one you better use test automation for. Many test cases that you still examine manually, can probably be automate, which can save you a lot of time.

Once you get decided which use case you ’ ll be performing manually you should determine when to test what, for example: group use cases ground on what is be tested (blind, login/logout, seafaring etc.).

Rule # 2 – Define your click path!

Go through all the use cases you hold decided upon and write down a click path for each one of them. Make sure you don ’ t forget any steps, even the most obvious ones, or you won ’ t be able to reproduce a bug and to reduplicate the precise same test on different devices.

How can you otherwise know, if an an topic appears exclusively on one device, if every time you make the “ same ” examination slenderly different?

Rule # 3 – Research the market!

When an app is free, it should flawlessly work on the most sold devices in the primary target market. The app should be tested on at least on 5 to 10 device, depending on the size of the quarry market. There are many different tools to aid you create your device pond, likegoogle developer consolethat can assist you specialize down the devices to choose from. An app that work perfectly on a twist that no one uses, will not drive your revenues!

Rule # 4 – Look for the correct characteristics!

Choose device with different characteristics, try to have as different device as possible, from ironware to software, from screen sizes to manufacturers.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Checking these things is very significant: not everyone has the late device or the latest software update.

Screens have many different screen sizes pixel resolutions, check if everything is exhibit in the right spot and correctly.

Apart from many different Android OS versions, many manufacturers also make changes in the UI and some functionalities, so make sure that your app is not affected by them!

The hardware characteristics are important when testing an app, so see adding more use event if you notice that you ’ re lose out on some things.

Rule # 5 – Keep your sessions short!

Try to organise your use cases so you can keep test sessions as abruptly as potential; try exclusively what you settle to test beforehand. If you cogitate of early things to test, just add them to the use cause list, don ’ t test them instinctively on the place. When performing long session, you may lose yourself in the app, make mistakes and invalidate the test.

Furthermore, if you get testing without a programme, you may forget to add all the stairs to your click path plan and you won ’ t be capable to repeat the like test on another gimmick.

Rule # 6 – Repeat

Perform the like precise test on all of the devices you chose for your manual nomadic testing. You ’ ll see how leisurely it is to just follow the same steps all over again. It will minimize the possibility of the “ human mistake ”.

Remember to repeat the same trial after any codification modification (something else might get broken while fixing)!

Rule # 7 – Document your bugs!

To dog your bugs expeditiously, when you find one, make certain to write down all the information you have gain and the exact thing you were make when you detected the malfunction. Only so you can easily test that constituent again after a bug has been fixed, instead of trying each and every exam again.

Documenting a bug will not only facilitate you keep track of the bugs but it will also make it easier to reproduce it. You can show the bug to your developers as many times as they need to understand where the trouble lie, assist them to fix it and accelerating the whole operation.

Conclusion

These 7 rules are more than just a checklist, they are meant to be a starting point of any new testing project, helping to structure your mentation and try idea. Structure is what helps you to keep everything under control at all times and to outline a open testing pattern, focussing only on the end. With manual mobile quiz those goals are: testing on the most suitable devices for your target market, choosing the right cause and retell the exact same tests on all of the chosen devices to find bugs.

Based on our research this is a testing structure that helps accomplish better results faster. You are probably already doing some or many of those things, but revising your structure is always a good idea. We get apply to do some things in a certain way and we lose vision of the bigger picture. Taking a step back and regroup your structure, bring the steps you realized were missing from your routine can give your mobile manual tests a clearer testing form, aid you to get a better examiner.

We have put together a cheat-sheet to help you get started with your manual testing and maintain your inquiry as well as your tryout results well organised. In this spreadsheet you will discover three sheet: one contains the didactics on how to use the other two sheet; the second sheet “ Research ” is where you decide which use cases you require to test and delimitate your click path for each use case. You will also have pie chart where you can input specific data ground on your target market and make a list of devices based on the data in the old section. The tertiary sheet “ Testing & amp; Tracking ” should be used during your testing session. The datum will be pull in from the previous sheet and the rest of the table are for you to occupy out click by chink during your examination.

Download this gratuitous cheat-sheet and start with your manual mobile essay today!