bugTeaser!!!

Love teasing bugs!!

Ah!Not so long back I had logged many issues for an app in the hope that it will for the betterment of the app. As always I worked hard and the app was something special for me so I took more care while testing, also making sure that giving appropriate "Suggestions/Feedback" wherever possible.

After some days the TM started reviewing of the bugs logged by me and my fellow members. The list of was indeed quite a big one so TM has a hard time. The problem was this app was the build was continuously updated for some minor issues and then given to the testing team. On the top of it, as always the release date is close by so we have to make sure that the app that is being shipped of good "Quality" not compromising on anything. Things were going good for me as almost all the BUGs logged by me getting 'Approved' by TM so I had time facing the development team. :) Not really!! We all are friends they were doing their job and I was doing mine.

The very next day once all of us reached to the office - we had a kick-off meeting (aimed at letting us know the current status of the app). Things were going good and that day some of my "Suggestions/Feedback" were kept 'on-hold' saying that it will be implemented in the next release - wherein I do not have any problem with that as I did my job to let them know. Now its their call whether they would like to go for these in this build or will be patched up in the next build. Almost 85% of bugs were already checked by TM and was happy with the work of his team. The same day in the second half I got an email saying that "Bug # was not approved". This is not a new thing but I wanted to know what reason was given to it in order to 'reject' it. I was shocked to see the reason as "computer/system specific issue". I hadn't got panic yet as I know I need to reproduce it and show it to TM on some other system or computer. I did that. The status got changed to 'on-hold' so I was pretty happy that its not rejected yet. This time in order to make it simple, clear and easy to understand, I attached a video clip in order to reproduce the issue - the steps taken by me. This time there was no email but my TM called me up for something. I went to his cabin to what is it? I was about to enter the room but I can still smell it what is it for?

I entered the room and my TM again showed me that he tried many systems and also seen my video clip but still they are unable to reproduce the bug. I asked his permission in order to try my hands on it so that I can show him how to reproduce the bug. To my surprise everything went smoothly and I was unable to reproduce it on his system. I started asking question to myself "Why","What wrong did I do?" I left the room quietly as I have nothing to say more. I continued with my work but still can not get the thing out of mind as in "Why not". All my BUGs are special for me so I make sure that everyone get a due respect. I checked the settings of the app on my system carefully to find out what did I do wrong when I was trying to reproduce the bug. Everything was find and I was again reproduce the bug on my system. I performed the task more than once and all the times I was successful. Later on after numerous tries I found that there is one setting that needs to be checked in order to replicate/reproduce the issue.

I again got up and started moving toward my TM's cabin. I seek permission from him to let me use system again for sometime. He happily handed over the system to me as he was almost done with his list. The first try went smoothly and he put a weird smile on his face. I closed the app and opened it again - I checked the settings to find out that there is a small check box which was not checked - for this scenario if this check box is not checked your app will work smoothly. So, I showed him what needs to be done in order to reproduce the bug. This time again the test did FAIL. I looked at my TM and he was having the same weird smile on his face this. I wondered what has happened but just to memorize that there is a bug that if you change something then you need to save it and re-start the app. (This issue was already being worked upon) I closed the app and opened again and this time the test failed - the issue with a small check box which was not checked so my test was getting PASSED. After showing him how to reproduce the bug my TM agreed and changed the status of bug in our bug reporting tool. The smile was no more there and I seek his permission so that I can go out of the cabin and continue with the work. I got out of his cabin keeping my head a little high on my shoulder as I did not put the weapons down once the bug was rejected but took the control and reproduced it. I went straight to get a cup of COFFEE (I am addicted to COFFEE) and just entered the cubicle where all my team members sits. I just asked them one question "Do you fight for your bug?"

Well, that was in my office and I will not tell you what responses I got from others and all. But, I have only one question for you all who will be reading this blog.

Do you fight for your bug?


Best Regards,

Amit

testing is my passion!!!
http://bugteaser.blogspot.com