Be Creative: Bug Hunting Advice From a Top Tester

Finding unique bugs in a software application is never easy. It’s even more difficult when you are working with dozens of other testers from around the world. In our latest guest post, uTester Amit Kulkarni – a recent Bug Battle winner – offers testers some advice for finding unique bugs when multiple issues have already been reported.

When working on test cycles in the uTest platform, it’s important to remember the model they follow. For instance, once the test cycle is open, it is made available to invited testers from all over the world, unless the customer has chosen specific criteria like geographical locatio, specialty, experience etc. And because there are different time zones, you may find yourself in a situation when you accept the invite for the test cycle and there are already a good number of bugs logged. So common, isn’t it?

Now here is the catch: Some testers wonder how do they go about it? There are already a lot of bugs logged, what should I do? How am I going to find a bug now? Well, first I would say calm down. Understand the application and what is expected from the test cycle. Once you are done with this, take a look at the bug reports already logged by other testers. This will give you an idea as to what part of the application has been tested so far, and what has yet to be tested.

I often feel quite lonely when there are no bugs logged when I accept an invite (a rare occurrence however). I would prefer to work with other testers as a team to make sure the outcome is what is expected by the customer before creating the test cycle, but that’s not always possible. That being the case, would you like to know how stand out from the other testers?

Here’s my advice:

Be Creative: In such situations you have to be creative with your test ideas. Think of scenarios that have not yet been tried. This is where you’ll save time by first understanding the duplicate bugs. It may sound hard, but it is time well spent in trying to understand the application and the scope for the test cycle. This creativity not only helps you for this particular test cycle, but will prove to be useful in other situations as well. So the point that you need to remember is this: Don’t just look for simple bugs.

Go through the other reports logged and try to reproduce the bug and see if you can dig deeper for serious bugs. It does help to generate quite a few new ideas if you take some time and spend in reading other tester reports.

Be Patient: This one of the key attributes for a tester – not only just for those working on uTest projects. Keep your cool, understand the application, and try to come up with test ideas that may yield some fresh insight. Because you are working with testers all across the globe,  it may possible that the test idea that you just thought of has been implemented by other tester, but that should not make you impatient.

Be an Explorer: Just don’t look out for the simple bugs that do not need much more exploration, although if you find them that is all well and good. Explore the application by targeting specific parts of the application. When you start exploring the application you will begin to distinguish the deeper issues, instead of bugs which are just on the surface.

While exploring the application makes sure that you are still very much in control of what are you trying to. At times exploration leads to the part of the application which is not yet suppose to test, so just be careful! Remember to read the scope of the test cycle before you do anything.

Be Agile: It is good to be agile, but it’s important not to lose your focus. Make sure that you are taking proper notes, taking screen shots or videos, or even using tools like Session Tester.

So, if you are ready to practice all the above then you are certainly going to have good time while working on the test cycles. Not to mention that it also helps you in planning/splitting your tasks as you move further along.

So, the next time if you accept an invite and see bugs logged, you got to know what to do, right?

Essential Guide to Mobile App Testing

Comments

  1. Matt says

    Great advise, common practices which tend to get forgotten in the heat of new test cycles and the rush to find bugs. I believe following these simple steps will also help to ensure the bugs you do submit are relative to the scope and are of a quality nature that is more likely to be approved and useful. There are a lot of GUI bugs submitted at the start of a project and the meat of any real issues take more investigations and testing skills. Anyone can find GUI bugs, but the technical, functional and even feedback bugs are what provide the real value in quality bug reporting. Not to downgrade GUI issues by any means, but these are usually easy to come by at the start and take little effort to find. I completely agree with Amit here that taking the time to read the submitted reports, the project’s scope and instructions, exploring the application under test to gain the best understanding of what the current environment is like and where the most effective area is to start will be. Building upon existing bugs reported is a great way to add value and not duplicate effort. Quality, not Quantity!

Leave a Reply

Your email address will not be published. Required fields are marked *