See below five tips that will help you to hold effective bug hunting.

Hunting season for bugs is open! 5 tips to succeed in bug hunting

#1. Don’t be afraid to break the rules.

You know perfectly that the mission of releasing the product that doesn’t have any bugs at all is impossible. It’s also impossible to cover all aspects of testing when testing by pre-defined test cases.
Our advice to the testers is: if you are using predefined test cases, make sure to explore functionality under test as well. Otherwise the possibility that you will miss some significant bug due to ‘inattentional blindness’ is really high.

#2. Explore the pattern!

It is a well known fact that the bugs have gregarious nature. They prefer to come together in groups. In the process of testing a new but resembling functionality, a tester should approach to his previous ideas and solutions. That is why it will be a good thing to write down somewhere the ideas that have already brought you a lot of good in the testing process.

#3. Hit the bug in its raw spot.

If you log the bug into your bug report as soon as you found it, you are wrong. This can be just the beginning but not the end.
Presence of a bug means that there is some loose link in your software system. You should take advantage of this instability of the system. Reduce the resources of the system; feed a great number of insane inputs and soon you will be able to see the appearance of other earlier and more dangerous bugs.

#4. Give an ear to the sounds of coming bugs.

Sometimes the appearance of the bug can be accompanied by various sounds. Therefore testers should always wear the headset in the process of bugs hunting. In such a manner they will not miss warning messages that cannot appear on their screen for some reason but nevertheless will inform testers about the bug appearance.

#5. Don’t be afraid or ashamed to ask your colleagues for help.

There are some cases when even the most brilliant tester cannot uncover the bug alone. In this case he should collaborate with his colleagues and hold the bug hunting process together. In such a way the tester may be able to generate ideas and to find some new solutions. Join Ubertesters on Facebook and shrare your questions and issues – our community is always ready to help!

These tips hopefully will help you to achieve the success in your bug hunting and to catch even more bugs that you have been catching before. Good luck in your bug hunting!

Are you ready to a bug hunting? Apply now to become professional Ubertester and start your testing career!

Comments
Harvey Specter
Posted at 7:22 pm January 23, 2015
Peter Kacandes
Reply
Author

I would also suggest that as part of your bug hunting strategy, there is a critical role of having a well developed app performance monitoring and management strategy in place. Of course you should have been doing that already as part of your development, QA, and test process to make sure that your app will perform well before you actually release it into the app store.
This will also help you identify bugs in production that you might have missed during dev, test, and QA. The problem with making any app idiot proof is that those idiots are so damn ingenious, so they will find things that you will never have thought of as part of your test strategy.
One of the key factors which will immediately kill your ability to grow a user base is if people download your app and then it provides a poor user experience, particularly with regard to performance, which may have nothing to do with you app itself, but could be a result of back end systems upon which your app depends.
You need to have a tool in place that allows you to track not only your app performance, but also that of all of your back-end and third party dependencies.
If people start downloading your app and have a bad experience, they will give you poor reviews, which will crush your growth strategies.
You need to be able to see and respond to fix issues before they cause your users problems such that they abandon your app and give it poor reviews.

Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>