Have you ever wondered how to find bugs effectively? Do you have your own set of test cases when looking for issues? In this post we will provide you with some helpful tips that testers can use when they do a bug test of an app and how they should hand in the bug. Sometimes when carrying out a simple test it is easy to overlook bugs. They can be very minimal, such as a graphic issue or missing link, or quite severe like crashes. In order to help you find them, we have come up with some tips:
- Use the app without Internet connection, in Wi-Fi mode and with 3/4G
- Switch Flight-mode/GPS/Bluetooth on and off
- Receive a call/text message
- Use music player/radio in the background
- Save results in the app, log out and log in again –> was everything saved correctly?
- Try using the app in places with bad signal (e.g. basements)
- Switch between portrait and landscape mode
- Change your location (in apps with GPS functionality)
- Use tethering while testing
- Turn off the device during the test
There is plenty more you can do, but this should give you an idea of how to look for things that are not supposed to happen. We call these scenarios “corner cases”.After finding a bug and checking that you’re the first to do so, submitting it is the next step. Did you know that the documentation of the bug is crucial for us? Our project managers need to be able to retrace all your steps and see the issue either in a screenshot, video or crash log. When handing in bugs, usually the following format is required:
- The title of the bug should include: First the section where you found the bug and then what kind of bug it is (e.g. Terminal area- Download is not working)
- Clear description: Please name every step that led to the bug. Where did it happen? And when? After which action?
- Add the expected and the actual result
- How often did it occur (e.g. 2 out of 5 times)?
- Always add screenshots or, in most cases even better, screencasts/videos
These are the standard factors we ask for in a test, on top of these each client requires more information, such as which network provider the bug was found on or the screen size of where the bug was, etc. Looking for bugs can be fun. Corner cases as well as the right documentation will help you maximize the outcome. What are your tips and tricks to find bugs? Feel free to share them in the comments!
Share it if you like it:
About the author
Other content that might be interesting for you:
Testbirds specialises in the testing of software such as apps, websites and Internet of Things applications by using innovative technologies and solutions. Under the slogan, “Testing Reality”, the company offers various testing methods to its clients looking to optimise the user-friendliness and functionality of their digital products. With over 250,000 registered testers located in 193 countries, Testbirds is one of the world’s leading crowdtesting providers. In addition, the IT service provider utilises cloud based technologies to support customers in the optimisation of their digital products. The combination of the two testing methods delivers a unique and extensive portfolio that takes the quality of software to the next level. Testbirds was founded in 2011 by Philipp Benkler, Georg Hansbauer and Markus Steinhauser. Today, the company has over 100 employees. Other than its headquarters in Munich, there are now offices in Amsterdam, London and Stockholm, franchises in Hungary and Russia and sales partners in Italy.
© Testbirds GmbH. All rights reserved.