Skip to main content
Back

11 tips on looking for bugs

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.

Back

11 tips on looking for bugs

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:

  1. Use the app without internet connection, in Wi-Fi mode and with 3/4/5G
  2. Switch flight-mode/GPS/Bluetooth on and off
  3. Receive a call/text message
  4. Use music player/radio in the background
  5. Save results in the app, log out and log in again – was everything saved correctly?
  6. Try using the app in places with poor reception or signal (e.g. basements)
  7. Switch between portrait and landscape mode
  8. Change your location (in apps with GPS functionality)
  9. Use tethering while testing
  10. 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 (and the 11th tip).

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?



Insights

We provide you with the latest insights from the world of crowdtesting

Stop guessing if your product meets your users' expectations and start making decisions based on facts.

Welcome to the autoverse
Automotive

Welcome to the Autoverse: Revolutionizing Connected Car Experiences

Marketing in a complex world
Crowdtesting

Marketing in a complex world: How crowdtesting can help you overcome the challenges

Press Releases

Testbirds sets new standards in information security with ISO 27001:2022 Certification

CX Trends 2024 featured
Crowdtesting

This time, it’s personal:
CX Trends for 2024

Why banking on crowdtesting is key for shaping secure, personalized experiences
Banking / Financial Services & Insurance

Why banking on crowdtesting is key for shaping secure, personalized experiences

Press Releases

Testbirds recognized as a representative vendor in Gartner’s Market Guide for Application Testing Services and Hype Cycle for UX

Learn how Testbirds empowered the customer experience in an app for a energy provider
Energy & Utilities

Empower your energy customers with an intuitive mobile app experience

Manufacturing

Testing AI for Success

Understanding the Customer Journey: Benefits, Touchpoints, and Optimization
Crowdtesting

Understanding the Customer Journey: Benefits, Touchpoints, and Optimization

Testbirds is certified by: