Guest Post: By Krishnaveni, one of the Top Testers at 99tests
The Open Bug Experience
A tester to some extent by nature of practice can effortlessly spot a flaw in a product or an application. And when this happens, it is very intriguing to voice out the same. But the question that bothers is – would the issue that was voiced out by the tester reach the right contact or not for the issue to be resolved?
A tester knows the impact, risk and consequence of a bug when it is present in a product or an application that is massively used by the public.
How about having a platform to voice the bugs that we come across in our daily activities, be sure that they reach the right contacts and be rewarded for the same too? Too good to resist isn’t it??
The recently launched “Open Bug” feature from 99tests facilities this.
About Open Bug
Open Bug is a very innovative initiative by 99tests, wherein the testers registered on 99tests can log bugs they come across. The bugs that are creative and worthy can be voted through which a tester is rewarded.
My Experience with Open Bug
The approach of Open Bug kindled my curiosity to give it a try.
Unlike the conventional process, wherein, we are accustomed to test a suggested app with a given mission, the interesting factor here is that a tester can choose any app and log the bugs. 99tests has always been a perfect platform for me to learn new things. Needless to say, I was sure that this open bug feature would definitely have more to offer me to learn.
What I learnt
The first thing I learnt was to leverage my skills I had, testing a particular genre of website (e-commerce, travel etc.,) and looked for apps belonging to that genre.
Secondly, I learnt to adapt my bug filing style based on the context for the open bug feature. Unlike the conventional ways, if the context was to just test a single app and log all the bugs for that app, then it would have made sense to file each bug individually. But the objective of the open bug feature was to test any app and expose the issues in them.
In order to accommodate this objective, I grouped the bugs based on its quality characteristic like usability, UI etc., and logged them as a single bug. However this would not apply in every case. Based on the need, some bugs like those of functionality had to be logged separately.
I was encouraged to try out the different genre of websites that I hadn’t tried before.
I got a couple of lessons from my mistakes. To err is human they say and I was no exception. And I committed mistakes too. Honestly it was an irony for me to realize that though I ventured to figure out flaws in other websites & products, I failed to ensure the same in what I was offering.
I have to admit that it was purely by oversight and I am not ashamed to admit it. I learnt what mistake I made and shall take care to overcome them going forward. And how did I realize it? Nah! I did not figure them out myself. Again by oversight. It was by other testers who viewed my bug and shared their comments on the same.
Guess at times one tends to have an oversight that they fail to notice the mistakes they make. Here are the mistakes I made.
Mistake #1: I had incorrectly keyed in the name of the website I tested.
Here, the bugs logged for the website were worthy, but how could one evaluate them when an incorrect website name is specified?
Mistake #2: For one bug, I had inadvertently included the link which was a report generated for another website.
Now though the bug was meant for one website and was valid, the incorrect report link I included for the same rendered the bug invalid.
The criteria in the open bug feature were to log a minimum of 20 bugs. So I went on a bug hunting spree and started to log the bugs I unearthed.
But after I reached a good number, I paused by and pondered; if doing this way really served the purpose the open bug feature was meant for? This is not a contest wherein I can just keep filing all the bugs of just one app at a go.
Now a question arose in my mind – what catches more attention of business owners to accept their app to be tested? Is it the few bugs that occur in some parts of their app or some major severity issues for them to be convinced to go in for a testing effort?
This thought has inspired me to focus on high priority issues that affect a business than just a technical bug. So this would mean that it’s important that one needs to log most critical bugs first.
It is motivating that any new thing attempted has many things to offer to learn.So this is an on going process testing – learning and improvising.Come give Open Bug feature a try and experience it for yourself. It’s worth every effort and time spent on it.